summaryrefslogtreecommitdiff
path: root/lib/public_key/include
Commit message (Collapse)AuthorAgeFilesLines
* Update copyright yearHenrik Nord2018-06-181-1/+1
|
* ssl,public_key: Provide details for CRL check failiures when revokation ↵Ingela Anderton Andin2017-07-071-1/+2
| | | | state can not be determined
* update copyright-yearHenrik Nord2016-03-151-1/+1
|
* Change license text to APLv2Bruce Yinhe2015-06-181-10/+11
|
* public_key: Export some dialyzer typesIngela Anderton Andin2014-02-061-21/+1
| | | | | Move dilayzer types from include file to erl file and use -export_type
* Fix incorrect use of public_key:private_key/0 typeTuncer Ayaz2014-01-281-1/+2
| | | | | | | | | | public_key:private_key/0 was referenced but undefined, and lib/ssl had a local definition of private_key/0. To fix that, make the following changes: * add public_key:private_key/0 type * document public_key/0 and private_key/0 * fix incorrect definitions and references
* ssl & public_key: Use standard nameIngela Anderton Andin2013-05-081-1/+1
|
* crypto: Deprecate functions, update doc and specsIngela Anderton Andin2013-05-081-1/+3
|
* PUBLIC_KEY: add support for Elliptic Curves to public_key appAndreas Schultz2013-05-081-0/+4
|
* All basic test cases passIngela Anderton Andin2013-01-111-2/+17
|
* Update copyright yearsBjörn-Egil Dahlberg2012-11-231-1/+1
|
* public_key: Added PKCS-10Fredrik Gustafsson2012-11-151-1/+1
|
* Add PKCS-8 support to public_keyIngela Anderton Andin2011-11-011-0/+1
|
* Implemented encode/decode support for ssh public key filesIngela Anderton Andin2011-03-241-5/+9
|
* Improved support for RSA and DSA public keysSeth Falcon2011-02-141-2/+3
| | | | | | | This patch allows the public_key module to decode and encode RSA and DSA keys encoded using the SubjectPublicKeyInfo format. When pem_entry_encode is called on an RSA or DSA public key type, the key is wrapped in the SubjectPublicKeyInfo format.
* Peer awarnessIngela Anderton Andin2010-09-291-0/+2
| | | | | | | Changed the verify fun so that it differentiate between the peer certificate and CA certificates by using valid_peer or valid as the second argument to the verify fun. It may not always be trivial or even possible to know when the peer certificate is reached otherwise.
* Improved certificate extension handlingIngela Anderton Andin2010-09-101-2/+4
| | | | | | | | | | | | | Added the functionality so that the verification fun will be called when a certificate is considered valid by the path validation to allow access to eachs certificate in the path to the user application. Removed clause that only check that a extension is not critical, it does alter the verification rusult only withholds information from the application. Try to verify subject-AltName, if unable to verify it let application try.
* Handling of path validation errors by the applicationIngela Anderton Andin2010-09-061-2/+9
| | | | | | | | | | | | | | | | | Changed the behavior of the verify_fun option so that the application can be responsible for handling path validation errors even on the server side. Also replaced the not yet documented validate_extensions_fun to be handled by the verify_fun instead. If the verify callback fun returns {fail, Reason}, the verification process is immediately stopped and an alert is sent to the peer and the TLS/SSL handshake is terminated. If the verify callback fun returns {valid, UserState}, the verification process is continued. If the verify callback fun always returns {valid, UserState}, the TLS/SSL handshake will not be terminated with respect to verification failures and the connection will be established. The verify callback fun will also be able to verify application specific extensions.
* Revise the public_key APIIngela Anderton Andin2010-08-231-0/+9
| | | | | Cleaned up and documented the public_key API to make it useful for general use.
* The R13B03 release.OTP_R13B03Erlang/OTP2009-11-201-0/+62