Persisting private/public key pairs in password-encrypted files for transportation to local cryptographic store
Number of patents in Portfolio can not be more than 2000
United States of America Patent
Stats
-
Oct 9, 2012
Grant Date -
Mar 16, 2006
app pub date -
Aug 24, 2004
filing date -
Aug 24, 2004
priority date (Note) -
In Force
status (Latency Note)
Importance
Abstract
Systems and methods for using private keys in software development that minimizes the risks of the private key being lost or stolen. A strong name consists of the assembly's identity, e.g., its simple text name, version number, and culture information (if provided), plus a public key and a digital signature. It is generated from an assembly file using the corresponding private key. The private/public key pair is persisting in a password-encrypted file using a standard encryption format that can be made available to everyone. The first time any subsystem of the development environment requires use of the private key contained in an encrypted file format, the developer is prompted to provide the password to decrypt the key. The user supplies the password and the public/private key is imported into a non-exportable key container in the local cryptographic store.
First Claim
Family
International Classification(s)
Cited Art Landscape
Patent Citation Ranking
Advertisement
Advertisement
Advertisement
Recipient Email Address
Recipient Email Address
Comment
Recipient Email Address
Add to Portfolio(s)
To add this patent to one, or more, of your portfolios, simply click the add button.
This Patent is in these Portfolios:
Add to additional portfolios:
Last Refreshed On:
Changes done successfully