[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 ]
Jogi Hofmüller
jogi at mur.at
Thu Dec 5 10:31:10 CET 2013
Dear all, Am 2013-12-04 12:57, schrieb Alex Band: > We would like to propose to put this functionality in maintenance > mode, meaning that it would be provided as it is without a service > guarantee. Alternatively, it could be removed altogether. This would > free us of a maintenance and support burden, meaning that we can > spend these resources on other valuable services. Totally agree. As far as I am concerned you could remove this feature altogether. > If the membership approves, the RIPE NCC could investigate ways to > implement true two-factor authentication for RIPE NCC Access. Nice. Regards! -- j.hofmüller aka Thesix >-<#!&$@@@? http://users.mur.at/thesix/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 230 bytes Desc: OpenPGP digital signature URL: <https://lists.ripe.net/ripe/mail/archives/ncc-services-wg/attachments/20131205/a2b08c61/attachment.sig>
- 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 ]