On 2012-05-04 09:03:19 +0100 (+0100), Jon Dowland wrote:
[...]
> So some form of access to the machine would be required to create
> the problem, be it physical or remote. The same access should be
> used to fix the problem.
[...]
I think this is part of the misunderstanding. If these systems are
nodes on an AX.25 network, what's being renamed (and potentially
broken) is the userspace binary which connects the machine to the
network. Think of it as if you're suggesting a rename of
/usr/sbin/sshd to /usr/sbin/secureshelld. Sure it's usually only
started from packaged scripts and managed configuration files, but
when it's also your only way into some remote systems that has a
much greater potential to render them indefinitely inaccessible.
--
{ IRL(Jeremy_Stanley); WWW(http://fungi.yuggoth.org/); PGP(43495829);
WHOIS(STANL3-ARIN); SMTP(fu...@yuggoth.org); FINGER(fu...@yuggoth.org);
MUD(kin...@katarsis.mudpy.org:6669); IRC(fu...@irc.yuggoth.org#ccl); }
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120504114234.gb...@yuggoth.org
