Sam Varshavchik wrote: | To summarize: | |A) The socket wire format used by authdaemon is really an internal |application format. It's not formally documented, per se. But since |the source code is -- obviously -- available it's not that difficult to |figure it out. | |B) Someone else figured out, well, most of it, and missed out a small |detail. As a result, their code does not work all the time. | |C) You want to make a useless kludge to authdaemon, just so that the |other code doesn't choke. | |What's wrong with this picture? |
Sam, you have suscinctly summarised the situation, of which I am glad. Which part of (B) have I missed? I need to see the UID down this socket!!
The part that instead of UID/GID authdaemon may return a single username instead, in which case the uid/gid comes from getpasswd() on the given username.
This is not rocket science.
pgp00000.pgp
Description: PGP signature
