So the plot thickens...

This leads to a very much more interesting question, which is, just
whose passwords were being attacked?  Was this an attack on the local
file, or could this be evidence of a zombie that is attacking other
systems somewhere in the world???

That "global" might not be pure hyperbole!


"Kenneth E. Lussier" wrote:

> gblo=Global Breaking Logic Operations . It's the primary logic
> engine that is used in several password cracking utilities such
> as John the Ripper, nutcracker, etc. What it does is it created
> passwords on the fly, encrypts them, and then tries to use them
> in a brute-force attack against a shadow password file.
>
> FYI,
> Kenny
>
>
> [EMAIL PROTECTED] wrote:
> >
> > People,
> > I had a question from someone who had been hacked.
> > They said:
> > > > we have a process that is running - /usr/lib/lib-gblo.1.3.so
> > > > that is taking up some massive CPU cycles.
> > > >  Do you know anything about this file?  Does it
> > > > exist on any of your systems?
> > > >
> > I can't find any reference to it. rpm -qf doesn't show anything.
> > They only install using rpms on a RH 6.x system.
> > Any thoughts?
> >
> > TIA,
> > Bob Sparks
> > Linux guru wannabe
> >
> > **********************************************************
> > To unsubscribe from this list, send mail to
> > [EMAIL PROTECTED] with the following text in the
> > *body* (*not* the subject line) of the letter:
> > unsubscribe gnhlug
> > **********************************************************
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************


**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to