Abstract:
A security infrastructure and methods are presented that inhibit the ability of a malicious node from disrupting the normal operations of a peer-to-peer network. The methods of the invention allow both secure and insecure identities to be used by nodes by making them self-verifying. When necessary or opportunistic, ID ownership is validated by piggybacking the validation on existing messages. The probability of connecting initially to a malicious node is reduced by randomly selecting to which node to connect. Further, information from malicious nodes is identified and can be disregarded by maintaining information about prior communications that will require a future response. Denial of service attacks are inhibited by allowing the node to disregard requests when its resource utilization exceeds a predetermined limit. The ability for a malicious node to remove a valid node is reduced by requiring that revocation certificates be signed by the node to be removed.
Abstract:
A security infrastructure and methods are presented that inhibit the ability of a malicious node from disrupting the normal operations of a peer-to-peer network. The methods of the invention allow both secure and insecure identities to be used by nodes by making them self-verifying. When necessary or opportunistic, ID ownership is validated by piggybacking the validation on existing messages. The probability of connecting initially to a malicious node is reduced by randomly selecting to which node to connect. Further, information from malicious nodes is identified and can be disregarded by maintaining information about prior communications that will require a future response. Denial of service attacks are inhibited by allowing the node to disregard requests when its resource utilization exceeds a predetermined limit. The ability for a malicious node to remove a valid node is reduced by requiring that revocation certificates be signed by the node to be removed.
Abstract:
Functionality is described that allows plural computing devices to share a master account. In one implementation, the functionality allows any candidate device to directly communicate with a communication system using the master account, providing that the candidate device satisfies a prescribed condition with respect to a master device. For example, the functionality can allow the candidate device to communicate with the communication system if it is within a threshold distance of the master device. In another implementation, the functionality instructs the master device and the candidate device to set up a tethering relationship. The functionality can then allow the candidate device to communicate with the communication system, via the master device, using the master account. In one implementation, the functionality can set up the tethering relationship without substantial (or any) involvement of the user (or users) who operate the master device and candidate device.
Abstract:
Functionality is described that allows plural computing devices to share a master account. In one implementation, the functionality allows any candidate device to directly communicate with a communication system using the master account, providing that the candidate device satisfies a prescribed condition with respect to a master device. For example, the functionality can allow the candidate device to communicate with the communication system if it is within a threshold distance of the master device. In another implementation, the functionality instructs the master device and the candidate device to set up a tethering relationship. The functionality can then allow the candidate device to communicate with the communication system, via the master device, using the master account. In one implementation, the functionality can set up the tethering relationship without substantial (or any) involvement of the user (or users) who operate the master device and candidate device.