In our testing we've found some occurrences of identd reporting back the wrong username for the owner of a socket. We added some instrumentation to identd so that we can tell it what we expect the u
/proc/net/tcp is an obsolete interface. It is inherently unreliable in that a record may be read using two read(2) calls. Those two calls may end up looking at two different records. So please use th
This isn't really the same issue. This looks like an euid vs. uid problem that reproduces every time. The problem we are seeing is a timing-window-race-condition kind of problem that happens maybe 1
In 2.4 it is entirely possible to have a record broken up into two reads. There is no guarantee that the two reads will be reading the same record. -- Visit Openswan at http://www.openswan.org/ Email
Let me make sure I understand what you're saying here... You're saying that since pidentd is calling fgets(), that can actually result in multiple read() calls. Because of this, the first half of th
fgets() is implemented on top of a buffered read, with my glibc it reads 4096 bytes. Whatever that size is, the second read is most likely going to be reading a partial record. There is no guarantee
Hello In our testing we've found some occurrences of identd reporting back the wrong username for the owner of a socket. We added some instrumentation to identd so that we can tell it what we expect