Anonymous Key Agreement Protocols Sample Clauses

Anonymous Key Agreement Protocols. To illustrate the usefulness of our proposed key agreement protocols, we now consider the scenario of delegates making and receiving phone calls on their mobile phones while international roaming. Before secure roaming can be established, the service provider must verify whether the roaming user is a legitimate subscriber with the respective home server. Conventional anonymous roaming mechanisms [1, 29] are rather inefficient as users would have to wait online while foreign telecommunication network communicates with the original home server to authenticate the users. These geographically distributed servers also generate extra network traffic during this process. At the same time, it is inconvenient to constantly renew the alias in an unlinkable manner to hide the identities. Our proposed key agreement protocols with the anonymity feature allow user to “hide” among a group of subscribers associated with the same home server. Moreover, after the home server has issued sets of matching public/private key pair at the very beginning, the home server is no longer required to be online. Our approach does not, however, appear to be scalable if one needs to hide among all (a potentially large set of) legitimate subscribers, and may not be flexible since it is natural that the set of subscribers is constantly changing. Both issues can be readily solved without an a priori group formation step. For example, any legitimate user will be able to spontaneously conscript an arbitrary group of users (i.e., without cooperation from other parties in the group) for each session. Such ad-hoc group formation empowers a user to have full control over the level of anonymity desired during the secure roaming establishment process. Although alias should also be used in our approach so that the list of users can be made available to users without revealing any user information, no renewal of alias (and possibly renewal of credential) is necessary as different invocations are unlinkable (guaranteed by the unconditional anonymity of our protocol).
View Source

Related to Anonymous Key Agreement Protocols

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? Yes

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: ▇▇▇▇://▇▇▇.▇▇▇▇▇▇-▇▇▇▇▇.▇▇▇/508.htm.

  • DISCLOSURE OF TBS ACCESS CODE TO THIRD PARTY (a) The Account Holder must exercise all care to ensure that the TBS Access Code is not disclosed to any person and shall take all steps to prevent forgery or fraud in connection with the use of his TBS Access Code and/or the operation of the TBS. If the TBS Access Code is disclosed to any person, the Account Holder must forthwith give the Bank written notice thereof, thereupon the Account Holder shall immediately cease to use the TBS Access Code. (b) Unless and until the Bank receives such written notice of disclosure, the Account Holder shall be fully liable and be bound by all transactions effected by the use of such TBS, with or without his consent or knowledge.

  • Freedom of Information and Transparency 20.1 The Recipient acknowledges that the Commissioner is subject to the provisions of the FOIA and agrees to assist and co-operate with the Commissioner (at the Recipient’s expense) where necessary to enable the Commissioner to comply with any requests received under the FOIA relating to this Agreement. This includes, but is not limited to, transferring to the Commissioner any request received by the Recipient under the FOIA relating to this Agreement as soon as practicable following receipt and in any event within three working days of receipt. 20.2 In no event shall the Recipient respond to a request under the FOIA relating to this Agreement without obtaining the prior written consent of the Commissioner. 20.3 The Recipient acknowledges that the Commissioner may be obliged to disclose information under the FOIA: 20.3.1 Without consulting the Recipient; or 20.3.2 Following consultation with the Recipient and having taken into account its views. Provided that where clause 20.3.1 applies the Commissioner shall, in accordance with the recommendations of the Secretary of State for Constitutional Affairs’ Code of Practice on the discharge of a public authorities’ functions under Part 1 of FOIA, take reasonable steps, to give the Recipient advanced notice or to draw the disclosure to the Recipient’s attention after any such disclosure. 20.4 The Recipient shall ensure it retains for disclosure all information (as defined in the FOIA) produced in the course of this Agreement or relating to this Agreement and shall allow the Commissioner to inspect such records from time to time upon request. 20.5 The Recipient acknowledges that the Commissioner is subject to certain transparency and disclosure obligations set out in the Elected Local Policing Bodies Specified Information Order 2011 (as amended) (“Transparency Obligations”) 20.6 The Recipient consents to the Commissioner publishing the contents of this Agreement and information regarding any tender process related to the Purpose of the Agreement to enable the Commissioner to comply with their Transparency Obligations. 20.7 The Recipient acknowledges that: 20.7.1 The Commissioner shall be responsible for determining, at their absolute discretion, whether any information is exempt from disclosure or should be disclosed pursuant to the FOIA and/or the Transparency Obligations and to what extent any information disclosed shall be redacted; and 20.7.2 Any lists or schedules provided by the Recipient outlining confidential information are of an indicative value only and that the Commissioner may be obliged to disclose confidential information in accordance with Clause 20.3 and/or Clause 20.5.

  • Genetic Information This plan does not limit your coverage based on genetic information. We will not: • adjust premiums based on genetic information; • request or require an individual or family members of an individual to have a genetic test; or • collect genetic information from an individual or family members of an individual before or in connection with enrollment under this plan or at any time for underwriting purposes.