Server Authentication Sample Clauses

Server Authentication. The Keeper Cloud Security Vault is protected by an API which authenticates each request from the client device. On the client device, a 256-bit "Authentication Key" is derived from the Master Password using PBKDF2-HMAC-SHA256 and a random salt. An "Authentication Hash" is generated by hashing the "Authentication Key" using SHA-256. To login, the Authentication Hash is compared against a stored Authentication Hash on the Cloud Security Vault. After login, a session token is generated and used by the client device for subsequent requests. This authentication token must be renewed every 30 minutes, or upon the request of the server. Transport Layer Encryption KSI supports 256-bit and 128-bit TLS to encrypt all data transport between the client application and KSI's cloud-based storage. This is the same level of encryption trusted by millions of individuals and businesses everyday for web transactions requiring security, such as online banking, online shopping, trading stocks, accessing medical information and filing tax returns. KSI deploys TLS certificates signed by Digicert using the SHA2 algorithm, the most secure signature algorithm currently offered by commercial certificate authorities. SHA2 is significantly more secure than the more widely used SHA1, which could be exploited due to mathematical weakness identified in the algorithm. SHA2 helps protect against the issuance of counterfeit certificates that could be used by an attacker to impersonate a website. KSI also supports Certificate Transparency (CT), a new initiative by Google to create a publicly auditable record of certificates signed by certificate authorities. CT helps guard against issuance of certificates by unauthorised entities. CT is currently supported in the latest versions of the Chrome web browser. More information about Certificate Transparency can be found at: xxxxx://xxx.xxxxxxxxxxx-xxxxxxxxxxxx.xxx. Keeper supports the following TLS cipher suites: • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA Key Pinning Keeper's native clients implement clients implement Key Pinning, a security mechanism which prevents impersonation by attackers using fraudulent digital certificates.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Server Authentication. We consider the known-(client)-key attack that the adversary tries to impersonate a server to a client whose private key is known i,j to the adversary, i.e. the chosen fresh oracle Πs is with i ∈ IDC and j ∈ IDS. Theorem 1 The protocol is secure against the known-client-key attack, provided the BDH assumption is sound, the hash functions are modelled as random ora- cles. Proof is presented in Appendix.
Sample 1Sample 2

Related to Server Authentication

  • Authentication This Note shall not be valid until authenticated by the manual signature of the Trustee or an authenticating agent.

  • Authorization, Authentication, and Access In order to ensure that access to the Data is limited to authorized staff, the Contractor must:

  • Access by and Authentication of Authorized Users Authorized Users of the Participating Institutions shall be granted access to the Licensed Materials pursuant to the following:

  • Execution and Authentication At least one Officer must sign the Notes for the Company by manual or facsimile signature. If an Officer whose signature is on a Note no longer holds that office at the time a Note is authenticated, the Note will nevertheless be valid. A Note will not be valid until authenticated by the manual signature of the Trustee. The signature will be conclusive evidence that the Note has been authenticated under this Indenture. The Trustee will, upon receipt of a written order of the Company signed by an Officer (an “Authentication Order”), authenticate Notes for original issue that may be validly issued under this Indenture, including any Additional Notes. The aggregate principal amount of Notes outstanding at any time may not exceed the aggregate principal amount of Notes authorized for issuance by the Company pursuant to one or more Authentication Orders, except as provided in Section 2.07 hereof. The Trustee may appoint an authenticating agent acceptable to the Company to authenticate Notes. An authenticating agent may authenticate Notes whenever the Trustee may do so. Each reference in this Indenture to authentication by the Trustee includes authentication by such agent. An authenticating agent has the same rights as an Agent to deal with Holders or an Affiliate of the Company.

  • Execution, Authentication, Delivery and Dating of Rights Certificates (a) The Rights Certificates shall be executed on behalf of the Company by any of its Chairman of the Board, President, Chief Executive Officer and Chief Financial Officer. The signature of any of these officers on the Rights Certificates may be manual or facsimile. Rights Certificates bearing the manual or facsimile signatures of individuals who were at any time the proper officers of the Company shall bind the Company, notwithstanding that such individuals or any of them have ceased to hold such offices either before or after the countersignature and delivery of such Rights Certificates.

  • AUTHENTICATION OF FACSIMILE BIDS The act of submitting a Bid by facsimile transmission, including an executed signature page or as otherwise specified in the Bid Documents, shall be deemed a confirming act by Bidder which authenticates the signing of the Bid.

  • Execution, Authentication, Availability and Dating of the Residual Certificates The Residual Certificates shall be executed on behalf of Xxxxxx Mae by an Authorized Officer of Xxxxxx Xxx under the corporate seal of Xxxxxx Mae, which may be in facsimile form and be imprinted or otherwise reproduced thereon, and shall be attested by the Secretary, Assistant Secretary, or a second Authorized Officer of Xxxxxx Xxx. The signature of any of these Persons on the Residual Certificates may be manual or facsimile. A Residual Certificate bearing the manual or facsimile signature of individuals who were at any time officers of Xxxxxx Mae shall bind Xxxxxx Xxx, notwithstanding that such individuals or any of them have ceased to hold such offices prior to the authentication and delivery of such Certificate or did not hold such offices at the date of such Certificate. At any time and from time to time after the execution and delivery of this Trust Agreement, Xxxxxx Mae may deliver Residual Certificates executed by Xxxxxx Xxx to the Certificate Registrar for authentication and the Certificate Registrar shall authenticate and make available such Certificates as provided in this Trust Agreement and not otherwise. No Residual Certificate shall be entitled to any benefit under this Trust Agreement or be valid for any purpose, unless there appears on such Residual Certificate a certificate of authentication substantially in the form provided for herein, executed by the Certificate Registrar by the manual or facsimile signature of one of its authorized signatories, and such certificate upon any Residual Certificate shall be conclusive evidence, and the only evidence, that such Residual Certificate has been duly authenticated and made available hereunder. Each Residual Certificate shall be dated the date of its authentication.

  • Execution Completion Authentication and Delivery (a) The Notes shall be executed on behalf of the Issuer by one or more officers of the Issuer authorized to do so pursuant to one or more resolutions of the Issuer, whose signatures may be manual or facsimile (an "Authorized Officer"). Notes bearing the manual or facsimile signature of an Authorized Officer shall bind the Issuer, notwithstanding that such person no longer serves as the official so authorized to execute the Notes prior to the authentication and delivery of the Notes or was not such an official at the date of execution of such Notes. The Global Agent shall have no responsibility to the Issuer to determine by whom or by what means a facsimile signature may have been affixed on the Notes, or to determine whether any facsimile or manual signature is genuine.

  • Executed and authenticated be executed manually or in facsimile by or on behalf of the Issuer and authenticated manually by or on behalf of the Fiscal Agent; and

  • Authentic Text This Agreement is drawn up in duplicate in the Danish, Dutch, English, Finnish, French, German, Greek, Italian, Portuguese, Spanish and Swedish languages, each of these texts being equally authentic.

Time is Money Join Law Insider Premium to draft better contracts faster.