[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] IPv6 support in the IP Analyser API
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Fri Dec 6 14:27:40 CET 2013
Alex, On Wed, 4 Dec 2013 12:57:26 +0100 Alex Band <alexb at ripe.net> wrote: > Since then, we have encountered several implementation, user > interface and support issues surrounding this feature, while it is > used by less than 0.7% of the users with a RIPE NCC Access account. > Most importantly, the functionality does not actually offer any > additional security. This is something that is provided by true > two-factor authentication. I'm curious how much access is actually done via X.509? That is to say, the 0.7% of users may be the most active ones, meaning that - for example - 25% of all RIPE NCC Access is done via X.509 authentication. (Or indeed it may be the opposite, with 0.1% of authentication done via X.509 certificates.) I think it is worthwhile getting this information before deciding one way or the other. Cheers, -- Shane
- Previous message (by thread): [ncc-services-wg] Authentication Proposal for RIPE NCC Access
- Next message (by thread): [ncc-services-wg] IPv6 support in the IP Analyser API
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]