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 ]
Peter Koch
pk at DENIC.DE
Wed Dec 4 14:54:09 CET 2013
On Wed, Dec 04, 2013 at 12:57:26PM +0100, Alex Band wrote: > Most importantly, the functionality does not actually offer any additional security. could you please elaborate on this assessment? > This is something that is provided by true two-factor authentication. Sure, _true_ two-factor authentication. I'd assume that since it's only .7%, the X.509 users (of which I am not one) are or have already been targetted directly? -Peter
- 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 ]