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]/
MD5 proposal
- Previous message (by thread): MD5 proposal
- Next message (by thread): MD5 proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrei Robachevsky
andrei at ripe.net
Tue Apr 2 10:28:21 CEST 2002
Ulf Kieber wrote: > Andrei Robachevsky writes: > >>>At the first character after the first white space (space or tab) >>> >>>>following the colon (":") >>>> >> >>>When submitting an update to the database that needs to be authorised using >>>this scheme, a "password:" pseudo-attribute must be used to submit a key >>>(passphrase). Line continuation is not allowed for this attribute, so the >>>whole key should fit on one line. If the key gets split across multiple >>>lines this will be treated as syntax error. >>> >> >>The value of the key starts at the first character after the first white >>space following the colon (":"). >> > > If I understand you and Engin's previous comment correctly, this would > change current behaviour, which is according to Engin's comment > > ``key starts after the first non-white space character after the colon'' > > Don't! This would most probably break people's scripts. > Sorry, I wasn't clear. ``Key starts at the first non-white space character after the colon''. That's how it works now. -- Andrei
- Previous message (by thread): MD5 proposal
- Next message (by thread): MD5 proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]