| Summary: | neatx doesn't protect custom ssh authorized_keys | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | David Sparks <davidsparks> |
| Component: | New packages | Assignee: | Gentoo NX Server project <nx> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Problem still exists in neatx-0.3.1_p59 authorized_keys will be protected as of neatx-0.3.1_p59-r2, just committed to CVS |
Neatx doesn't protect its ssh authorized_keys file so when neatx is upgraded it is replaced with the default key provided in the package. This prevents logins that use a custom key from working until authorized_keys is restored. Please consider adding /var/lib/neatx/home (${NX_HOME_DIR}) to CONFIG_PROTECT. I hope this shows what the problem is: ca-desktop1 # ls -l ~nx/.ssh/ total 8 -rw------- 1 nx root 1899 Sep 30 14:08 authorized_keys (re-emerge neatx) ca-desktop1 # ls -l ~nx/.ssh/ total 8 -rw------- 1 nx root 629 Sep 30 22:09 authorized_keys