full-disclosure - !SPAM! Automated ssh scanning

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <6d456c36040826093640c68eba@mail.gmail.com>
From: tremaine at gmail.com (Tremaine)
Subject: !SPAM! Automated ssh scanning

On Thu, 26 Aug 2004 09:43:13 -0500 (CDT), Ron DuFresne
<dufresne@...ternet.com> wrote:
> On Thu, 26 Aug 2004, Richard Verwayen wrote:
> 
> > On Thu, 2004-08-26 at 15:12, Todd Towles wrote:
> > >  The kernel could be save. But with weak passwords, you are toast. Any
> > > automated tool would test guest/guest.
> > >
> > Hello Todd!
> >
> > You are right about the passwords, but guest is only a unprivileged
> > account as you may have on many prodruction machines. But they managed
> > to become root on this machine due to a kernel(?) exploit!
> > Should I then consider any woody system to be insecure to let people
> > work at?
> 
> 
> If your uasers are not trustable, then they should not have access to
> local systems of yours.  Once a person has a shell, then they are 95% to
> root.
> 
> Thanks,
> 
> Ron DuFresne


Fair point... but it would still be nice to determine precisely how
they are getting root access so preventative measures can be taken and
the hole plugged.
-- 
Tremaine
IT Security Consultant