On Thu, 27 Jan 2011, elbbit wrote:
> On 27/01/11 16:21, will trillich wrote:
> > That's quite an assertion. How can I confirm it HAS been compromised, as
> > opposed to thinking it's a possibility?
>
> There is no way to know for sure unless you dissect the code running the
> machine. Depending on
On 27/01/11 16:21, will trillich wrote:
> That's quite an assertion. How can I confirm it HAS been compromised, as
> opposed to thinking it's a possibility?
There is no way to know for sure unless you dissect the code running the
machine. Depending on your paranoia quotient you will either reinsta
That's quite an assertion. How can I confirm it HAS been compromised, as
opposed to thinking it's a possibility?
On Thu, Jan 27, 2011 at 9:44 AM, Henrique de Moraes Holschuh wrote:
> On Tue, 25 Jan 2011, will trillich wrote:
> > In kern.log there's only
> > Jan 23 23:04:59 darth kernel: [640847
On Tue, 25 Jan 2011, will trillich wrote:
> In kern.log there's only
> Jan 23 23:04:59 darth kernel: [64084756.601774] exploit[25161]: segfault at
> 10c00b ip sp deadc01d error 6
> Jan 23 23:05:08 darth kernel: [64084765.528734] NET: Registered protocol
> family 5
There is no mistery. Yo
On 26/01/11 20:58, Bob Proulx wrote:
> will trillich wrote:
>> 23:58:11 up 583 days, 3:03, 6 users, load average: 0.00, 0.02, 0.08
> You have not rebooted your system in 583 days meaning that you have
> NOT taken any of the posted Linux kernel security upgrades in that
> time period. You may h
will trillich wrote:
> Never seen this before -- all daemons and all user processes killed. Zap. It
> happened around 23:17 Chicago time (that's when the log-daemons quit
> logging). What would cause this?
> ...
> will@darth:~$ uptime
> 23:58:11 up 583 days, 3:03, 6 users, load average: 0.00, 0
Ooh, hadn't noticed that. "I'm sorry, Dave, I'm afraid I can't do that..."
:)
So... Nobody else has had a weird
shut-down-all-user-processes-and-all-daemons event? I must be special!
On Wed, Jan 26, 2011 at 1:58 PM, elbbit wrote:
> On 26/01/11 01:26, will trillich wrote:
> > In kern.log there'
On 26/01/11 01:26, will trillich wrote:
> In kern.log there's only
> Jan 23 23:04:59 darth kernel: [64084756.601774] exploit[25161]: segfault at
> 10c00b ip sp deadc01d error 6
Am I the only one to see "Dead Cold" in there? That error code right
THERE is
Never seen this before -- all daemons and all user processes killed. Zap. It
happened around 23:17 Sunday, Chicago time (that's when /var/log/* abruptly
stopped). Any idea what might cause this?
I was ssh'd in to my Debian server and... disconnected. No problem, I was
using *screen* to *vim* some
On Monday 24 January 2011 01:47:27 will trillich wrote:
> Never seen this before -- all daemons and all user processes killed. Zap.
> It happened around 23:17 Chicago time (that's when the log-daemons quit
> logging). What would cause this?
[ ... snippage ... ]
>
> *Anybody got a clue as to what m
Hi,
frank thyes wrote:
On Mon, 2011-01-24 at 00:47 -0600, will trillich wrote:
583 days
Up since then... if the box is reachable from the internet I would'nt
trust it and move on to reinstall. Is's much quicker then wasting your
time analyzing this strange behaviour.
What I don't understand
On Mon, 2011-01-24 at 00:47 -0600, will trillich wrote:
> 583 days
Up since then... if the box is reachable from the internet I would'nt
trust it and move on to reinstall. Is's much quicker then wasting your
time analyzing this strange behaviour.
Bye
Frank
--
To UNSUBSCRIBE, email to debian-
Never seen this before -- all daemons and all user processes killed. Zap. It
happened around 23:17 Chicago time (that's when the log-daemons quit
logging). What would cause this?
I was ssh'd in to my Debian server and... disconnected. No problem, I was
using screen to vim some Catalyst modules, s
13 matches
Mail list logo
