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/ncc-services-wg@ripe.net/
[ncc-services-wg] [db-wg] RIPE Database Release 1.72 - including SSO Integration
- Previous message (by thread): [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration
- Next message (by thread): [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Tue Mar 25 10:23:28 CET 2014
Hi, Op 25 mrt. 2014, om 09:55 heeft Gert Doering <gert at space.net> het volgende geschreven: > Hi, > > On Tue, Mar 25, 2014 at 09:43:21AM +0100, Agoston Horvath wrote: >> Denis was referring to the web forms, that are also named 'syncupdates' and 'webupdates'. >> The actual syncupdates service did not change. >> >> Furthermore, the syncupdates and webupdates web forms were already enforcing https because of sensitive authentication data (e.g. passwords). The only change >> that happened yesterday was that now we also enforce https on the query form, so that the RIPE Access session token is secured. > > Thanks for the clarification. This is far less intrusive than the original > mail made me believe, and I think it's a reasonable change which should > not have any adverse effects. I fully agree. Thanks for the clarification! Sander
- Previous message (by thread): [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration
- Next message (by thread): [ncc-services-wg] [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]