Re: New Debian Single Signon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello,
I tried the manual way [1] which works, but please fix the following:
In the text ist says to try the following:
curl --key <username>.key --cert <username>.cert
https://sso.debian.org/spkac/test/env
Please change the certificate filename extension to .crt (from .cert)
to match the actual file downloaded. Otherwise copy & paste won't work
(due to a "missing" cert file) and people might get confused.
Simon.
[1] https://sso.debian.org/spkac/enroll_manually/
Am 2015-08-26 um 16:25 schrieb Enrico Zini:
> Hello,
>
> I've set up a prototype of the new sso.debian.org based on client
> certificates, and I'd like your opinion on its accessibility.
> Details of the new setup are here:
> https://lists.debian.org/debian-devel/2015/08/msg00539.html and
> some more documentation is here:
> https://wiki.debian.org/DebianSingleSignOn#Debian_SSO_documentation-1
>
>
>
To use the new setup, you go to
> https://sso.debian.org/spkac/enroll/, log in with your Debian Web
> password, and use that page to add a certificate to your browser.
>
> After that you can visit contributors.debian.org and nm.debian.org
> without needing to log in, until the certificate expires.
>
> This seems to work smoothly with FireFox and Chromium; however, I
> could not find out how to make links and lynx work with client
> certificates.
>
> So, here are my questions:
>
> - have you been using sso.debian.org before? With which browser? -
> can you use the new certificate-based version? With which browser?
> - any other comments?
>
> (I am not subscribed to this list: please try to keep me in Cc)
>
> Enrico
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJV3qahAAoJEBy08PeN7K/pV1wQALeFvp/eGC671UIvme/erv/C
cbEkarfgWjK1K2U+MqY4HsmJTCSmXKtvioGnrEulEgIt2OfpRZ1PJnykkqqF8jK5
jg/DfPfsFpMVlane7D65ZO6t62T93Pw004RFzx3D42Ga5Z3KUXsoxD0sMjGSZul0
8UMDiJn3fc0K9cs/D5qakk/IP9J/hfPPjoPzcfBtnMRUaMyXG0hIXboCJnoLvAam
qS2aNNA6WwmBqKyO2VFlRr7OIXiLQMeW9yC0A0qpWe2hdpFayNTV97OOg4qKwpm9
RFRn4tgJFJUKjqPso1xejgt6F7MLY+m7/DhzOxNkGBCw+TEZ43EUBNsuEEeuBGQb
627Zj1QB/NHuLv5NSQJuQS0UIhtnaM0Ah9qiJiQODRX8fpp5UE5yRq9TJivbbWXa
HuvzVVfnPfeC89SqqExVRo7n6WLFhl20vtgW5s//vZb8Ki3z+p1hDxaqvfGmPPQG
bA+l4zdbUNJWtHbvbLikY/hkTlPC6INqKn3R2B3hbPxQvLpIDTmnRoO3RTC1PQuo
IRg3q2w+GiqRx0M3JX/Z6PEoQnc+qbszOS1kT5HMD9k3K3GZJ6JXhaeYjPS+1TwB
xv3QXOq9pvtR4HU2OYjnq3N9MNZrritiA1dX1VOkKdRvSHvmdavlgVryh+DJiyKP
q7h0iRaoV9Pj/P4zj4kx
=KWPw
-----END PGP SIGNATURE-----
Reply to: