| 1 |
I did do some upgrading the other day... forget what now. But, just to be safe, I emerge |
| 2 |
rkhunter and ran it... came up clean. Hell, I probably restarted a daemon or two in the |
| 3 |
last few days. I would feel more comfortable knowing exactly what printed that to the log, |
| 4 |
but I'm not going to sweat it too much. |
| 5 |
|
| 6 |
b |
| 7 |
|
| 8 |
|
| 9 |
Lance Lassetter wrote: |
| 10 |
> Ouch, I'm not the one with this problem but would something like |
| 11 |
> rkhunter which is recommended to be used by the -hardened team pick up |
| 12 |
> something like this? |
| 13 |
> |
| 14 |
> I run with standard with 'rkhunter -c' do I need to specify other |
| 15 |
> options with rkhunter? |
| 16 |
> |
| 17 |
> Thanks, |
| 18 |
> |
| 19 |
> Lance(stuNNed) |
| 20 |
> |
| 21 |
> On Mon, 2005-03-21 at 10:52 -0500, Wes Kurdziolek wrote: |
| 22 |
> |
| 23 |
>>When you upgrade certain packages, part of their post-install is to tell |
| 24 |
>>init to restart b/c it or its configuration has changed. However, if |
| 25 |
>>you haven't upgraded any of these packages (off the top of my head, I'm |
| 26 |
>>not sure which, but I'd guess sysvinit would be a good start) it could |
| 27 |
>>be a sign of someone installing a trojan init. |
| 28 |
>> |
| 29 |
>>On Sat, 2005-03-19 at 10:08 -0800, Ben Munat wrote: |
| 30 |
>> |
| 31 |
>>>Anyone know why this: |
| 32 |
>>> |
| 33 |
>>>init: Trying to re-exec init |
| 34 |
>>> |
| 35 |
>>>would show up in my logs? |
| 36 |
>>> |
| 37 |
>>>Ben |
| 38 |
>>>-- |
| 39 |
>>>gentoo-server@g.o mailing list |
| 40 |
>>> |
| 41 |
>> |
| 42 |
>>-- |
| 43 |
>>gentoo-server@g.o mailing list |
| 44 |
> |
| 45 |
> |
| 46 |
> -- |
| 47 |
> gentoo-server@g.o mailing list |
| 48 |
> |
| 49 |
|
| 50 |
-- |
| 51 |
gentoo-server@g.o mailing list |
Archives