This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-services-wg] Authentication Proposal for RIPE NCC Access
- Previous message (by thread): [ncc-services-wg] Authentication Proposal for RIPE NCC Access
- Next message (by thread): [ncc-services-wg] Authentication Proposal for RIPE NCC Access
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lutz Donnerhacke
lutz at iks-jena.de
Thu Dec 5 10:42:42 CET 2013
* Alex Band wrote: > The way this system is implemented, an LIR Portal user with admin rights > can issue X.509 certificates to users. However, they cannot be forced to > use it. Also, a passphrase is optional, meaning that it’s not really > two-factor. Whatever you smoke, stop it! Using certificates to authenticate is not and never was a two-factor method. The authentication scheme only proofs the possing of a private key. In which form the key is stored locally is outside of the scheme. You simply can't check this property.
- Previous message (by thread): [ncc-services-wg] Authentication Proposal for RIPE NCC Access
- Next message (by thread): [ncc-services-wg] Authentication Proposal for RIPE NCC Access
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]