Identity-Based Cryptography Sample Clauses

Identity-Based Cryptography. ‌ Identity-based cryptography (ID-PKC) was introduced by Shamir [54] in 1984, and en- xxxxx communicating users to verify signed data without exchanging private or public keys, without managing certificates, and without having to rely on services provided by a third party. It assumes the existance of a private key generator (PKG) from which users are issued their private keys. Once all private keys have been issued, the PKG can be closed for an indefinite period while the network can continue to function as normal (as long as no additional users are introduced). This is because the system does not intro- duce key revocation as in traditional PKI, and therefore always assumes that keys are valid. In the identity-based system, public keys are derived from a known identity such as the username or e-mail address, and thus may be generated by anyone. In order to obtain the private key, an entity needs to present itself to a private key generator. The PKG combines its master key with the identity value of the challenging entity and generates the private key. It is crucial to the identity-based scheme that the PKG is trusted as it will know every user’s private key, and thus be able to decrypt any message sent in its domain. This property is called key escrow and is by many considered a shortcoming of identity-based cryptography. However, there are also cases in which key escrow may be a needed property, such as in the health care profession where an audit trail to transactions may be a legal requirement. Shamir’s motivation in developing the identity-based cryptosystem was originally to simplify key management in e-mail systems. Because a user generally knows the e-mail address of the recipient, it implies that the user also would know the public key. En- crypting the message using the public key would require the recipient to obtain the corresponding private key from the PKG. The sender may also sign the message using the appropriate private key. Upon reciept, the receiver may easily verify a signature only by knowing the identity of the sender. It is also important to note that public and private keys are generated independently, unlike in traditional PKI. Although the notion of identity-based cryptography is quite old and has co-existed with PKI for many years, it wasn’t until recently when Boneh and Franklin [9] demon- strated the construction of very efficient and provably secure identity-based primitives using elliptic curve pairings that ID-PKC truly gain...

Related to Identity-Based Cryptography

  • Cryptography Supplier will maintain policies and standards on the use of cryptographic controls that are implemented to protect Accenture Data.

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.

  • Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Bus Drivers The provisions of this Article apply to school term bus drivers except as hereinafter modified. Bus Drivers are guaranteed a base of one thousand and ninety (1090) hours per school year. Guarantee consists of 1090 hours divided by possible working days in a school year times actual number of days worked. This excludes Saturday and Sunday and General Holiday trips. (a) Regular shift is defined as the conveyance of passengers to school in the morning and home in the afternoon. (b) Extra shift is defined as the conveyance of passengers for extra-curricular activities. (c) Shifts shall be paid at a minimum of two (2) hours and drivers' time will be uninterrupted if less than one-half (½) hour remains between shifts. (i) Drivers are entitled to one 15 minute rest period after two (2) hours of work and a second rest period after six (6) hours of work. Paid waiting times of 15 minutes or more will be construed as a paid rest period regardless of the length of time spent waiting. (d) All work after nineteen hundred (1900) hours on those days on which the regular shift has been worked shall be deemed to be overtime. After twelve (12) hours from the start of the regular shift, work will be deemed as overtime. (e) Hours of work consisting of regular and extra shifts and overtime are shared as equally as possible amongst drivers. Each driver has the opportunity to choose a percentage of the work available beyond one’s guaranteed hours, although the decision of the Employer will prevail. If no drivers are available, other transportation department staff may share the work. (f) Where School District transportation is used for extra-curricular trips on Saturdays and Sundays, the following applies instead of the overtime rates in Article 10.2: (i) Time and one-half (1 ½) regular rate for driving to and from destination. (ii) Upon arrival at destination, waiting time shall be paid at the regular rate of pay. (iii) No shift will be paid less than four (4) hours. (iv) Trips that are cancelled where the driver positions into departure point/school shall be paid at two (2) hours at one and one half (1 ½) times the regular rate. (v) All work carried out in this sub paragraph 9.5(f) shall be on a volunteer basis and shared as equally as possible. All Transportation employees may participate and shall be paid at the Bus Driver rate of pay. (vi) An exception to 9.5 (f) (i) to (iv) above will apply to bus driving on ski trips. Bus drivers who drive on ski trips shall share those hours only with other registered ski trip drivers. (g) Work carried out on General Holidays shall be paid in accordance with the current contract rates. (h) At the end of each school year a review of school bus drivers’ hours of work will be made to ensure minimum guarantee is met. Any shortages will be paid out.

  • Indicator Home and Community Care • Reduce wait time for home care (improve access) • More days at home (including end of life care) Percent of Palliative Care Patients discharged from hospital with home support Sustainability and Quality • Improve patient satisfaction • Reduce unnecessary readmissions Overall Satisfaction with Health Care in the Community SCHEDULE 6: INTEGRATED REPORTING‌ General Obligations‌

  • Metadata Where the Contractor has or generates metadata as a result of services provided to the Province, where that metadata is personal information, the Contractor will: not use it or disclose it to any other party except where the Agreement otherwise specifies; and remove or destroy individual identifiers, if practicable.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.