"Niels M�ller" wrote:
>
> Thayne Harbaugh <[EMAIL PROTECTED]> writes:
>
> > Okay, that works. Now is there some ACL or something that I can
> > put the key in so that I don't have to use --sloppy to connect or
> > is that somthing not yet implimented?
>
> Not yet implemented. I haven't yet decided how the ACL database should
> look like, but it might be something like appending the acl to
> ~/.lsh/known_hosts. If so, you can use --capture-to ~/.lsh/known_hosts.
> But I don't want to make it too easy to trust keys by default.
>
> > These might be useful (although I don't think they're the
> > most current):
>
> Do you want me to include the init-script in the distribution? If so,
> where? Would it make sense to create a contrib directory, and a file
> contrib/lshd.rhlinux.init?
Sounds good.
> I don't know much about redhat's packaging conventions, so I don't
> know what is convenient for you.
Wow - convenient for me - didn't know you cared ;^). The only thing
I can think of that would be more convenient is to have your packaging
set the Version: tag in the lsh.spec file to match the version of
the software (PS - you might want to set the Release: to be "1"
rather than "ns1"). If the lsh.spec file matches the rest of the
software (right now it does but things might change in the future
and it will have to be maintained) then people will be able to
build an RPM straight from a source tar ball as if the source tar
ball was a source RPM - cool stuff.
Thanks.
>
> /Niels
