Re: [vchkpw] Fields' use?
On Nov 20, 2004, at 1:17 AM, Tom Collins wrote: On Nov 19, 2004, at 6:33 PM, shadowplay.net wrote: um.. the uid and gid are used on a unix file systems to identify permission levels of access to files and directories. they allow an administrator to compartementalize access on a *nix box. they are closely tied with the applications chmod chown and chgrp. Perhaps you should have read the rest of this thread before posting. In the case of vpopmail, the fields are called pw_uid and pw_gid but they are used for other purposes. We had considered renaming pw_gid to pw_flags, but as Ken pointed out previously, there's too much code that refers to the field by its old name, pw_gid. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/ Can't we make both point to the same location in memory? Yet have them behave the same way? If the change were done in a major revision, then people might accept it. Once you know what it does, it does not seem to be a logic name for the variable, but you get used to it. X-Istence
Re: [vchkpw] Fields' use?
X-Istence wrote: On Nov 18, 2004, at 3:44 PM, Matthew Walker wrote: What are the pw_uid and pw_gid fields in the user info actually used for? I did a quick read through the docs, and couldn't find any information about what they do other than the fact that they're the user id and group id. Matthew They are named to confuse people. :P Actually i have no clue, but there should be some documentation on them, and they should possible be renamed to something more suiting for the task they are doing or being used for. The GID field is used for setting user flags, such things like NO_PASSWD_CHNG NO_POP NO_SMTP NO_WEBMAIL NO_IMAP BOUNCE_MAIL NO_RELAY NO_DIALUP Don't know how the work, never used them. Look in the src, vmoduser.c for info. DAve -- Systems Administrator http://www.tls.net Get rid of Unwanted Emails...get TLS Spam Blocker!
RE: [vchkpw] Fields' use?
um.. the uid and gid are used on a unix file systems to identify permission levels of access to files and directories. they allow an administrator to compartementalize access on a *nix box. they are closely tied with the applications chmod chown and chgrp. pw_uid is == uid from the /etc/passwd file same with pw_gid they were probably not identified in documentation because they are pretty evident if you came from an *nix file system admin background they do have the added benefit of being used as a reference for the functionality that dave pointed out. kenneth gf brown X-Istence wrote: On Nov 18, 2004, at 3:44 PM, Matthew Walker wrote: What are the pw_uid and pw_gid fields in the user info actually used for? I did a quick read through the docs, and couldn't find any information about what they do other than the fact that they're the user id and group id. Matthew They are named to confuse people. :P Actually i have no clue, but there should be some documentation on them, and they should possible be renamed to something more suiting for the task they are doing or being used for. The GID field is used for setting user flags, such things like NO_PASSWD_CHNG NO_POP NO_SMTP NO_WEBMAIL NO_IMAP BOUNCE_MAIL NO_RELAY NO_DIALUP Don't know how the work, never used them. Look in the src, vmoduser.c for info. DAve
Re: [vchkpw] Fields' use?
On Nov 19, 2004, at 6:33 PM, shadowplay.net wrote: um.. the uid and gid are used on a unix file systems to identify permission levels of access to files and directories. they allow an administrator to compartementalize access on a *nix box. they are closely tied with the applications chmod chown and chgrp. Perhaps you should have read the rest of this thread before posting. In the case of vpopmail, the fields are called pw_uid and pw_gid but they are used for other purposes. We had considered renaming pw_gid to pw_flags, but as Ken pointed out previously, there's too much code that refers to the field by its old name, pw_gid. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [vchkpw] Fields' use?
Matthew Walker wrote: What are the pw_uid and pw_gid fields in the user info actually used for? I did a quick read through the docs, and couldn't find any information about what they do other than the fact that they're the user id and group id. Hi, At least the gid is used to store information related to not allowing smtp, not allowing pop, not allowing imap access etc etc. Regards, Rick
Re: [vchkpw] Fields' use?
On Nov 18, 2004, at 3:44 PM, Matthew Walker wrote: What are the pw_uid and pw_gid fields in the user info actually used for? I did a quick read through the docs, and couldn't find any information about what they do other than the fact that they're the user id and group id. Matthew They are named to confuse people. :P Actually i have no clue, but there should be some documentation on them, and they should possible be renamed to something more suiting for the task they are doing or being used for. X-Istence
Re: [vchkpw] Fields' use?
On Thursday 18 November 2004 6:47 pm, X-Istence wrote: On Nov 18, 2004, at 3:44 PM, Matthew Walker wrote: What are the pw_uid and pw_gid fields in the user info actually used for? I did a quick read through the docs, and couldn't find any information about what they do other than the fact that they're the user id and group id. Matthew They are named to confuse people. :P Actually i have no clue, but there should be some documentation on them, and they should possible be renamed to something more suiting for the task they are doing or being used for. I picked the field names to match the standard /etc/passwd field names. The pw_uid field is no longer used. It was orginally used to enable/disable APOP support. But that code was re-written and no longer requires a field. The pw_gid field is also a bit mask. Each of the bits are defined in vpopmail.h. Look for the gid flags section. Each flag is fairly self explanatory. Renaming the fields would break all the current code and programs that use these fields, so it probably isn't a good idea. The last two gid flags that were added, as far as I know, are the NO_SPAMASSASSIN and DELETE_SPAM flags. These might only be in the 5.5 (devel) version. I'm not sure if it has made it into the 5.4 versions, even though we use it all the time. Ken Jones
