| View previous topic :: View next topic |
| Author |
Message |
dmotzev
n00b
Joined: 22 Jan 2006
Posts: 1
|
 Posted: Sun Jan 22, 2006 6:51 pm Post subject: grsec kills snmp with signal 6. help! |
 |
|
Hi there!
As stupid as it sounds, this was working fine with 2005.0... I migrated a key machine of my network to 2005.1 and now I can in no way execute the snmp daemon. The backtrace led nowhere - at first try to access /dev/urandom, snmpd get killed my grsec with signal 6. Meanwhile snmpwalk reports this:
| Code: |
snmpwalk: stack smashing attack in function netsnmp_udp_transport()
Aborted
|
And the grsec kernel log says this:
| Code: |
Jan 22 20:43:06 alphred grsec: From 85.187.214.196: signal 6 sent to /usr/sbin/snmpd[snmpd:10755] uid/euid:0/0 gid/egid:0/0, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0
|
Just my guess - I might have messed up the grsec kernel config but I don't quite believe it. Anyway, any ideas will be greatly appreciated!
Cheers!
Dan |
|
| Back to top |
|
 |
Sunthief
n00b
Joined: 22 Dec 2005
Posts: 34
Location: Grand Forks, BC
|
| Posted: Tue Feb 14, 2006 9:19 pm Post subject: |
|
|
I just had the same problem on one of my AMD64 machines. I looked all over for the fix but there doesnt seem to be much help anywhere on the net. heres what I did that fixed the problem:
| Code: | | USE="-tcpd -perl -ssl -ipv6" emerge net-snmp |
I tried it first with removeing the ssl & ipv6, so it must of been either the perl or the tcpd that messed me up. Let me know if it works for you. Dont forget you can do a
| Code: | | emerge -pv net-snmp |
To see what flags are being used. Then try removing them one at a time till it works. GL
_________________
Nick Muzzio
www.sunthief.com
------------------------------------------
Sun E-250 Enterprise Server
Dual 400Mhz 64bit Ultra Sparc CPU's
2GB Ram |
|
| Back to top |
|
|
eclipse99
n00b
Joined: 03 Oct 2004
Posts: 22
|
| Posted: Wed Apr 05, 2006 4:11 pm Post subject: It Worked For Me Too! |
|
|
I had the same errors as you had and now it runs fine.
What could be the issue here?
My USE flag for ipv6 was disabled so this isn't the problem... |
|
| Back to top |
|
|
eclipse99
n00b
Joined: 03 Oct 2004
Posts: 22
|
| Posted: Mon Sep 25, 2006 9:23 am Post subject: Solved! |
|
|
I don't know exactly why but I found a solution:
| Code: | | USE="-perl -ssl -tcpd" emerge net-snmp |
|
|
| Back to top |
|
|
didl
Retired Dev
Joined: 09 Sep 2003
Posts: 1106
Location: Pittsburgh, PA
|
| Posted: Mon Sep 25, 2006 1:16 pm Post subject: |
|
|
This has nothing to do with grsec! grsec only logs the fact
that the executable was killed by signal 6. The real trouble
maker is ssp (stack-smashing-protector). This could either
be due to a real stack smashing attack or a simply an ssp
"bug". If you're willing to sacrifice ssp you could switch
your gcc to a non-ssp profile which should solve this problem. |
|
| Back to top |
|
|
|
Networking & Security
