search for: pathping

On Sat, 23 May 1998, Torkil Zachariassen wrote: > >I have browsed various versions of libc and found a handful of weak points > >where the value of an enviroment variable is trusted more than necessary. > [1] > Could you explain to programming novices on linux-security - people like > myself 8) - hwo this could affect security on a firewall (proxy and/or > IP-router,

-----BEGIN PGP SIGNED MESSAGE----- ============================================================================= FreeBSD-SA-00:53 Security Advisory FreeBSD, Inc. Topic: catopen() may pose security risk for third party code Category: core Module: libc Announced:

Can anyone tell me where my blunder is in the following program? llvm-as reports: llvm-as: testit.ll:11: Can't store 'opaque *' into space of type 'opaque *'! Which doesn't seem to make sense to me. What is it that is illegal about storing a pointer to opaque in a space that is of type pointer to opaque? Is it just that you can't store pointers to opaque? %path =

...Tc qdisc add dev eth1 root cbq bandwidth 100Mbps avpkt 1500 Then I add filters for rsvp, for example: Tc filter add dev eth0 parent 8000: protocol ip rsvp Tc filter add dev eth1 parent 8001: protocol ip rsvp But, on my windows XP box, when I try to pathping -n -R the linux box, it says the linux box is not RSVP AWARE. Can someone give-me a hint on what am I doing wrong here ? Also, can someone clarify me as if linux RSVP supports UDP encapsulation as the Standard RSVP provides on ports 1698,1699 ? (RFC2205) Any help appreciated. Thank you...

There are security holes in XMCD 2.0pl2 (and presumably all previous versions), a popular audio cd player for numerous unix platforms, which allow a user defined environment variable to overflow a fixed size buffer resulting in a complete compromise of system security on machines with XMCD installed suid root. The cddb_init() function reads in the environment variable XMCD_CDDBPATH, and parses

Alexander O. Yuriev wrote: > > Your message dated: Wed, 20 Nov 1996 18:04:39 EST > > >has anyone played with the securelevel variable in the kernel and the > > >immutable flags in the ext2 file system? > > > > Yes, and its actualy quite nice. > > > > >The sysctrl code seems to allow the setting of the flag > > >only by init (PID=1)