Re: Human readable .ssh/known_hosts?

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

 




At this point, my best practice would possibly be, to start with an
empty known host and build a new one from all hosts in my .ssh/config.

You could move your user-known hosts file to the global location,
and empty yours.
That way new (and changed) get written to your new file, but the old
list is used as a backup.

Perhaps that would be a feature request - "also look at this file,
and silently migrate to the user's file if identical".



How would a 'lasst_seen' column in known_hosts be a nice feature? I'm not sure.

Not sure about that. Age doesn't tell about validity.
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev



[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux