Re: UCD-4.2.2 and UCD-4.2.3 snmptrapd verification

["Laurence Brockman" <laurence () fluxinc com>]

The copy of glibc I'm running is glibc-2.2.4. I've encountered the same
problems as dotslash when using the following command:
snmptrapd -f -n -P, where the key is the -P (Print out to stderr) I think.

This is on an Intel running patched version of RedHat 7.2

Laurence


----- Original Message -----
From: "Wes Hardaker" <wjhns55 () hardakers net>
To: "KF" <dotslash () snosoft com>
Cc: <vuln-dev () security-focus com>; <recon () snosoft com>; "Laurence Brockman"
<laurence () fluxinc com>
Sent: Monday, February 18, 2002 12:15 AM
Subject: Re: UCD-4.2.2 and UCD-4.2.3 snmptrapd verification


> > > > > > On Sat, 16 Feb 2002 10:39:14 -0500, KF <dotslash () snosoft com> said:
> dotslash> so far on UCD-4.2.2 I have the following... I am now looking
> dotslash> at 4.2.3 something is definately wrong in the logging
> dotslash> functions of both when compiled from the .tar.gz... the
> dotslash> default mandrake binary did not have this issue, I
> dotslash> recompiled it on my own. I have my config.cache and
> dotslash> snmptrapd.conf if anyone wants them.
>
> Just taking a guess here, but is your glibc up to date?  I think I've
> narrowed your problem down to a bug in vsnprintf and I don't think
> it's in the ucd-snmp code itself.
> --
> "Ninjas aren't dangerous.  They're more afraid of you than you are of
them."
>