.ssh configuration gets deleted with every update

[Stefanr]

We renamed our AuthorizedKeysFile in /etc/ssh/sshd_config. This file containing our custom key file is present in /var/lib/nxserver/home/.ssh, but it gets deleted after every update as per freenx-server.postinst. We feel this directory should be left alone after initial configuration.

[Marcelo Boveto Shima (marceloshima)]

Currently, the key handling is made by "$sudo dpkg-reconfigure
freenx-server".
In the current scenario you should copy your keys to
/var/lib/nxserver/home/custom_keys,
then select "Custom Keys" when reconfiguring.

Maybe a different approach is needed.

On Thu, Dec 4, 2008 at 7:42 AM, Stefanr <email address hidden> wrote:

> Public bug reported:
>
> We renamed our AuthorizedKeysFile in /etc/ssh/sshd_config. This file
> containing our custom key file is present in
> /var/lib/nxserver/home/.ssh, but it gets deleted after every update as
> per freenx-server.postinst. We feel this directory should be left alone
> after initial configuration.
>
> ** Affects: freenx-server
> Importance: Undecided
> Status: New
>
> --
> .ssh configuration gets deleted with every update
> https://bugs.launchpad.net/bugs/305091
> You received this bug notification because you are a member of FreeNX
> Team, which is the registrant for FreeNX Server.
>
> Status in FreeNX open source NX Server: New
>
> Bug description:
> We renamed our AuthorizedKeysFile in /etc/ssh/sshd_config. This file
> containing our custom key file is present in /var/lib/nxserver/home/.ssh,
> but it gets deleted after every update as per freenx-server.postinst. We
> feel this directory should be left alone after initial configuration.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~freenx-team<https://launchpad.net/%7Efreenx-team>
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~freenx-team<https://launchpad.net/%7Efreenx-team>
> More help : https://help.launchpad.net/ListHelp
>

[Marcelo Boveto Shima (marceloshima)]

If this behavior is a bug please reopen.