On 19 Mar 2001, Colin Marquardt wrote:
> Daniel Pittman <[EMAIL PROTECTED]> writes:
>
>> I believe that a more typical place is in `~/.authinfo'. I intend to
>> support .authinfo for passwords under TRAMP2, as well as completion
>> from that file.
>
> Cool, thanks.
>
>> If people think that /etc/hosts is a better choice, though...
>
> I don't know. There is ~/.rhosts too. Maybe it should be per-method
> customizable?
Hrm. A hook for each protocol to support it. Not /too/ hard to
implement. Then each protocol could support one (or more) locations.
Which is pretty cool. I like the idea.
> E.g., with ssh, ~/.rhosts is deprecated, but there would be
> ~/.ssh/known_hosts (and maybe even ~/.ssh/authorized_keys) in
> addition, both with a different syntax.
Yup.
> Best suggestion is probably to make it flexible so that people can
> add to it. File name spec and a regexp to get the host name should be
> sufficient.
Actually, my plan would be to provide a protocol property that let you
define the function(s) to call to do completion. Then, writing a few
generic completion methods (.authinfo, /etc/hosts) would be cool.
Maybe even including a hook to add to the standard lists, to make it
easy for users to configure. Hrm.
Since it's a little way off[1], there is time for more though.
Daniel
Footnotes:
[1] Right after I figure out what is making here-documents under bash
on Linux corrupt the input in a semi-random fashion. That's the hold-up
for safe writing at the moment and is considerably higher on my priority
list than user interface.
--
Books won't stay banned. They won't burn. Ideas won't go to jail. In the
long run of history, the censor and the inquisitor have always lost.
-- A.W. Grisold
