Torsten Neuer (email@example.com)
Thu, 15 Jul 1999 08:48:26 +0200
According to Frank Guangxin Liu:
>I have some ideas about this username/password thing.
>We can put those information in a separate file (only
>readable to root, or whoever runs the "htdig" task).
>The password file can have three columns,
>siteURL username password
>Multiple lines are allowed so that "htdig" can dig different
>sites(URL) with different username/password. This is an improvement
>over the old htdig where only ONE username/password can be
>We can also make a special entry for "siteURL" column, say,
>a dash "-", or a word "default", which means that this line
>(username/password) will be used if no matching siteURL entry
>can be found for a site that requires authentication.
>We can even modify the -u option to "htdig". If this option
>has : in it (say username:pass), use the old way, otherwise,
>treat it as the filename of the password file. If it has a
>leading /, treat it as an absolute filename, otherwise, a
>filename relative to CONFIG_DIR
If we are going to use such a file, we could possibly also use
existing resources, like the ftp ~/.netrc file. However, this
could imply splitting up ht://Dig configuration and access in-
formation, which might not be useful.
-- InWise - Wirtschaftlich-Wissenschaftlicher Internet Service GmbH Waldhofstraße 14 Tel: +49-4101-403605 D-25474 Ellerbek Fax: +49-4101-403606 E-Mail: firstname.lastname@example.org Internet: http://www.inwise.de
------------------------------------ To unsubscribe from the htdig mailing list, send a message to email@example.com containing the single word "unsubscribe" in the SUBJECT of the message.
This archive was generated by hypermail 2.0b3 on Wed Jul 14 1999 - 23:10:06 PDT