Re: [hylafax-users] PAM and owner names

[Lee H. <fa...@ho...>]

Chris Weiss wrote:

> actually, I'm writing my own client and setting the RCVFMT to have the
> "o" field as per http://www.die.net/doc/linux/man/man1/faxstat.1.html.
> The owner field shows up as "10" which is the UID of the uucp user in 
> my passwd.


And the particular file being highlighted is probably owned uucp.uucp, 
and in the recvq that's all that hfaxd has to go on: the UID and GID of 
the files themselves.  There's nothing else to tell it who "owns" any of 
those files.

> My goal is to have a custom faxrcvd script that chowns the files to
> the various users.


 From my understanding this should be possible - except remember that 
the *users* being discussed are those in 
/var/spool/hylafax/etc/hosts.hfaxd... unless maybe you're using PAM... 
in which case I don't know if this is supposed to work as expected... 
because PAM just says "yes" or "no"... I think.  I'm not sure that it 
can pass back other information or not.

I've not looked into it much to see if this is for sure how it works, 
but I would guess that if it doesn't find the user in hosts.hfaxd then 
it merely displays the GID number.  And from my read on the manpages 
it's the GID that you'll want to modify, not the UID.  So chgroup 
instead of chown.

> I guess I don't really need to use PAM, but it would be nice to pass
> the user management off to others via webmin/usermin instead of
> writing my own user management as well.


Yes, it would be nice not to have multiple data stores for the user 
information.  I'm fuzzy on the details of what you're trying to do... 
it's mostly uncharted territory I'd think.

> Also, is there some doc on the protocol?


No, not really.  There's what you see in hylafax-server or 
hylafax-client and then the best starting point is always looking at 
'sendfax -vv' output.  But, no, the protocol is not exhaustively 
documented.  It's mostly ftp-like, and ftp is documented.  As for the 
job-related parameters those are custom to hfaxd protocol, and if you 
need more details about them it's usually best to just learn via 
trial-and-error or read the hfaxd code a bit.  I do not disagree that 
good documentation on the protocol would be good to have.

Lee.