Re: Long Exim break-in analysis

To: debian-security@lists.debian.org
Subject: Re: Long Exim break-in analysis
From: Izak Burger <isburger@gmail.com>
Date: Wed, 22 Dec 2010 14:41:50 +0200
Message-id: <[🔎] AANLkTikGvysh5i+wnNzoOYH7UQi9FRvF11uxdCT5z1Yi@mail.gmail.com>
In-reply-to: <[🔎] AANLkTinE=WG_6L4LVzHewJAgMZKjwwB5N595LU=TzYmk@mail.gmail.com>
References: <[🔎] 201012212307.37241.vladislav.kurz@webstep.net> <[🔎] AANLkTi=XOTx6CowzQzjhy-X1M+Mae6RJazeKQWGrvFy7@mail.gmail.com> <[🔎] 20101222120613.GA2794@wavehammer.waldi.eu.org> <[🔎] AANLkTinE=WG_6L4LVzHewJAgMZKjwwB5N595LU=TzYmk@mail.gmail.com>

http://www.reddit.com/r/netsec/comments/en650/details_of_the_root_kit_that_go

With the exception of replacing /etc/exim4/exim.conf, its pretty much
exactly what happened to me :-)

Reply to:

References:
- Long Exim break-in analysis
  - From: Vladislav Kurz <vladislav.kurz@webstep.net>
- Re: Long Exim break-in analysis
  - From: Izak Burger <isburger@gmail.com>
- Re: Long Exim break-in analysis
  - From: Bastian Blank <waldi@debian.org>
- Re: Long Exim break-in analysis
  - From: Izak Burger <isburger@gmail.com>

Prev by Date: Re: Long Exim break-in analysis
Next by Date: Re: Long Exim break-in analysis
Previous by thread: Re: Long Exim break-in analysis
Next by thread: Re: Long Exim break-in analysis
Index(es):
- Date
- Thread