full-disclosure - SSH Exploit Request

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20031116015651.GA18683@arobas.net>
From: vladimir at arobas.net (Vladimir Parkhaev)
Subject: SSH Exploit Request

Quoting Valdis.Kletnieks@...edu (Valdis.Kletnieks@...edu):
> 
> And yes, *your* ssh can still go away if something else does a runaway and runs
> the system out of swap space. Although many vendors have an out-of-memory
> handler that does the best thing most of the time, none of them do the best
> thing ALL the time. And even if it doesn't, the system may be simply thrashing
> itself to death but *not* actually killing anything..

<more end-of-the-world-scenarios deleted>

Valdis, you forgot to mention some other cases in which 
upgrading SSH can take down a production server. Those include:

1. Upgarding SSH while having sex.
2. Droping a server in a bathtub full of hot water right after the upgrade.
3. Aliasing 'sshd' to '\rm -rf /' ans typing sshd.
and many many more...

The fact is, upgrading sshd (not XYZ!) does not require reboot and does
not affect any other processes that server runs. If you don't beleive
me, just... try it :)

-- 
.signature: No such file or directory