courieruserinfo is a utility for retrieving user account information.
Account information is accessed through the courier-authlib authentication
library.
===> The following configuration options are available for courieruserinfo-1.1.2_1:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
NOTES FOR RUNNING COURIERUSERINFO
In order to use courieruserinfo, it must be able to access the
authdaemon domain socket, named 'socket'. When courieruserinfo runs as
root, this presents no problem. However, if you need to run courieruserinfo
as a non-root user, you have three options, all of which require some
manual work.
Option 1: Add the user courieruserinfo will run as to the group that
owns the authdaemon socket directory in /etc/group. More than one user
can be added to the group vector in this way. This arrangement works
well if courieruserinfo will be run by only a small number of users.
If the authdaemon socket directory is owned by courier:courier and you
run courieruserinfo as user vmail, your /etc/group file will have a line
something like this:
courier:x:465:vmail
Option 2: Some programs, such as tcpserver, allow you to separately set
the uid and gid of programs they call but don't honour the group vector
found in /etc/group. If you invoke courieruserinfo from such a program,
set the gid to the group ownership of the authdaemon socket directory.
Option 3: Change the permissions on courieruserinfo to set gid to the
group ownership of the socket directory. Again, if the socket directory
is owned by courier:courier, change the ownership and permissions
of courieruserinfo like so:
chgrp courier courieruserinfo
chmod g+s courieruserinfo
Be aware that this will allow any user on the system to access user
account information through courieruserinfo.
To mitigate possible security risks posed by running courieruserinfo
setgid, courieruserinfo cannot retrieve passwords.
The location of the authdaemon domain socket is listed in the
authdaemonrc configuration file as the parameter authdaemonvar.
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
security/courier(passd,passwd,userinfo): Unbreak fetch and cleanup
The maintainer provided a new download location for his three ports after
a site reorganization broke fetching for two of them. In addition to
updating the MASTER_SITES, other cleanups where performed:
* Trim Headers
* Convert USE_GMAKE to USES+=gmake
* Convert NOPORTDOCS to options DOCS
* Removed unterminated string in courierpassd makefile
* Removed empty strings in courierpassd makefile
PR: ports/179670
Approved by: bapt / culot (mentors, implicit)
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )