ap22-mod_auth_pam
Hello. I've been using mod_auth_pam everywhere for years. Yet I cannot seem to get it to work on a 7.2/i386 box of mine. Here's what I get when I try to start it: httpd: Syntax error on line 104 of /usr/local/etc/apache22/httpd.conf: Cannot load /usr/local/libexec/apache22/mod_auth_pam.so into server: /usr/local/libexec/apache22/mod_auth_pam.so: Undefined symbol "pam_end" Any hint? bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ipsec-tools fix broken in CURRENT
Hi, this patch file ipsec-tools_fbsd90.txt
Fix broken ipsec-tools in freebsd 9.0-current.
Because after change syscons stop compiling sources.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=149270
>Category: ports
>Responsible:freebsd-ports-bugs
>Synopsis: ipsec-tools is broken in CURRENT
>Arrival-Date: Wed Aug 04 12:40:04 UTC 2010
--
M.Punov
-
AITNET - Sofia/Bulgaria -
Software & Network Solutions
(+359) 888 73 73 58;(+359) 2 402 4000
Index: Makefile
===
RCS file: /home/ncvs/ports/security/ipsec-tools/Makefile,v
retrieving revision 1.26
diff -u -r1.26 Makefile
--- Makefile20 Mar 2010 15:12:15 - 1.26
+++ Makefile4 Aug 2010 11:18:17 -
@@ -60,7 +60,7 @@
.include
.if ${OSVERSION} > 97
-BROKEN=fails to build with new utmpx
+LDFLAGS+= -lulog
.endif
.ifdef(WITH_DEBUG)
--- work/ipsec-tools-0.7.3/src/racoon/isakmp_cfg.c 2008-11-27
17:25:20.0 +0200
+++ work/ipsec-tools-0.7.3/src/racoon/isakmp_cfg_new.c 2010-08-04
14:58:27.0 +0300
@@ -38,7 +38,8 @@
#include
#include
-#include
+#include
+#include
#if defined(__APPLE__) && defined(__MACH__)
#include
#endif
@@ -1651,8 +1652,7 @@
int inout;
{
int error = 0;
- struct utmp ut;
- char term[UT_LINESIZE];
+ char term[8];
char addr[NI_MAXHOST];
if (usr == NULL || usr[0]=='\0') {
@@ -1665,33 +1665,20 @@
switch (inout) {
case ISAKMP_CFG_LOGIN:
- strncpy(ut.ut_name, usr, UT_NAMESIZE);
- ut.ut_name[UT_NAMESIZE - 1] = '\0';
-
- strncpy(ut.ut_line, term, UT_LINESIZE);
- ut.ut_line[UT_LINESIZE - 1] = '\0';
-
GETNAMEINFO_NULL(raddr, addr);
- strncpy(ut.ut_host, addr, UT_HOSTSIZE);
- ut.ut_host[UT_HOSTSIZE - 1] = '\0';
- ut.ut_time = time(NULL);
-
plog(LLV_INFO, LOCATION, NULL,
"Accounting : '%s' logging on '%s' from %s.\n",
- ut.ut_name, ut.ut_line, ut.ut_host);
-
- login(&ut);
+ term, usr, addr);
+ ulog_login(term, usr, addr);
break;
case ISAKMP_CFG_LOGOUT:
-
plog(LLV_INFO, LOCATION, NULL,
"Accounting : '%s' unlogging from '%s'.\n",
usr, term);
- logout(term);
-
+ ulog_logout(term);
break;
default:
plog(LLV_ERROR, LOCATION, NULL, "Unepected inout\n");
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ipsec-tools fix broken in CURRENT
Hi, this patch file ipsec-tools_fbsd90.txt
Fix broken ipsec-tools in freebsd 9.0-current.
Because after change syscons stop compiling sources.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=149270
>Category: ports
>Responsible:freebsd-ports-bugs
>Synopsis: ipsec-tools is broken in CURRENT
>Arrival-Date: Wed Aug 04 12:40:04 UTC 2010
--
Michael Pounov
Index: Makefile
===
RCS file: /home/ncvs/ports/security/ipsec-tools/Makefile,v
retrieving revision 1.26
diff -u -r1.26 Makefile
--- Makefile20 Mar 2010 15:12:15 - 1.26
+++ Makefile4 Aug 2010 11:18:17 -
@@ -60,7 +60,7 @@
.include
.if ${OSVERSION} > 97
-BROKEN=fails to build with new utmpx
+LDFLAGS+= -lulog
.endif
.ifdef(WITH_DEBUG)
--- work/ipsec-tools-0.7.3/src/racoon/isakmp_cfg.c 2008-11-27
17:25:20.0 +0200
+++ work/ipsec-tools-0.7.3/src/racoon/isakmp_cfg_new.c 2010-08-04
14:58:27.0 +0300
@@ -38,7 +38,8 @@
#include
#include
-#include
+#include
+#include
#if defined(__APPLE__) && defined(__MACH__)
#include
#endif
@@ -1651,8 +1652,7 @@
int inout;
{
int error = 0;
- struct utmp ut;
- char term[UT_LINESIZE];
+ char term[8];
char addr[NI_MAXHOST];
if (usr == NULL || usr[0]=='\0') {
@@ -1665,33 +1665,20 @@
switch (inout) {
case ISAKMP_CFG_LOGIN:
- strncpy(ut.ut_name, usr, UT_NAMESIZE);
- ut.ut_name[UT_NAMESIZE - 1] = '\0';
-
- strncpy(ut.ut_line, term, UT_LINESIZE);
- ut.ut_line[UT_LINESIZE - 1] = '\0';
-
GETNAMEINFO_NULL(raddr, addr);
- strncpy(ut.ut_host, addr, UT_HOSTSIZE);
- ut.ut_host[UT_HOSTSIZE - 1] = '\0';
- ut.ut_time = time(NULL);
-
plog(LLV_INFO, LOCATION, NULL,
"Accounting : '%s' logging on '%s' from %s.\n",
- ut.ut_name, ut.ut_line, ut.ut_host);
-
- login(&ut);
+ term, usr, addr);
+ ulog_login(term, usr, addr);
break;
case ISAKMP_CFG_LOGOUT:
-
plog(LLV_INFO, LOCATION, NULL,
"Accounting : '%s' unlogging from '%s'.\n",
usr, term);
- logout(term);
-
+ ulog_logout(term);
break;
default:
plog(LLV_ERROR, LOCATION, NULL, "Unepected inout\n");
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Whither Thunderbird 3.1(.1)?
On 03.08.2010 20:52, Doug Barton wrote: > On 08/03/10 09:59, Joe Marcus Clarke wrote: >> On 8/3/10 3:05 AM, Beat Gaetzi wrote: >>> On 03.08.2010 02:59, Doug Barton wrote: Just curious about the status of native Thunderbird 3.1.x. IMO the linux version is a significant improvement over 3.0.x, so I'd like to run the native version and get out of "clunky font land" sometime soon. :) Do y'all have a roadmap? If I missed it, my apologies ... >>> >>> Thunderbird 3.1 is ready since it has been released but the update >>> depends on this repo-cpoy: >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148136 >> >> Ugh. With all my travel and work lately, the repocopies moved to cvs so >> I missed them in my weekly sweep. Sorry. I just took care of this. >> >> Joe >> >>> >>> In the meantime you could use the port from our development repository: >>> # svn co >>> https://trillian.chruetertee.ch/svn/freebsd-gecko/trunk/mail/thunderbird > > Careful, if you guys start rewarding my whinging about stuff you'll just > get more of it. :) > > Meanwhile, hopefully ale can coordinate with y'all on the enigmail > plugin since they made a break on compatibility and enigmail 1.0.x only > works with tbird <= 3.0.x, and enigmail 1.1.x only works with tbird >= > 3.1.x. Woo hoo! Please take a look at this patch which updates enigmail-thunderbird to 1.1.2 and works with Thunderbird 3.1: http://people.freebsd.org/~beat/patches/enigmail-1.1.2.patch ale: Could you please consider committing this patch? Thanks, Beat ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ap22-mod_auth_pam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/10 10:48, Andrea Venturoli wrote: > Hello. > I've been using mod_auth_pam everywhere for years. > Yet I cannot seem to get it to work on a 7.2/i386 box of mine. > > Here's what I get when I try to start it: > > httpd: Syntax error on line 104 of /usr/local/etc/apache22/httpd.conf: > Cannot load /usr/local/libexec/apache22/mod_auth_pam.so into server: > /usr/local/libexec/apache22/mod_auth_pam.so: Undefined symbol "pam_end" ldd /usr/local/libexec/apache22/mod_auth_pam.so Looks like my AP_FAST_BUILD= yes AP_GENPLIST=yes sweep broke it. I'll revert / fix this later today, in the meantime, just use the previous version of the port. - -- - 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iD8DBQFMWYb2dbiP+9ubjBwRAkMcAJ4qlAIq159+VMDUw0590YMyGytbuwCghO6D ascao/b/XMWAznNMX4p0LyA= =+v5O -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Whither Thunderbird 3.1(.1)?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just for the sheer sake of saying it since its the least I can do for this, I would like to say thanks to the gecko team for all the nice work. Having email with a nice project integrated like lightning means a world of difference for a lot of people if not just me. For the FreeBSD Project to have invaluable tools at-hand like these is priceless and speaks for it self among all the features and tools available. So with a final word, Thanks. Regards, - -- jhell,v -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBAgAGBQJMWZUFAAoJEJBXh4mJ2FR+6S4H/3YXokrFYjg+bFARmyEmP0B4 wds5X9IygWH0XoZgbBTQ1RAmTZ31BbsjPeOzrwFjUZYeikW/nNDWrrqM+NoZPoFl jtIORjSnbVJRQUpRUn/68GTUiQfJWPyv2QhpJThoJLcrgTWGxQXD5wM4I2HbEe2W Vords8kE+89QcZci63lQ/sAYjOtqmNXbTZ7wtRHFqofrkwPHXJpExWouZjwKZ73b M9a9ikf9yOtmZCxH75KFEDj6VdKjXDqMaDeY9fc9ogDTVxpMuKbHWXYOukvP2NG5 l3MDOveHHL/93mxc+hXM9Zui9h1eK6OOrXRukKRLKtbVM2Fc1txMZb7x4/mNflA= =J2M7 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
:${foo_enable:=NO} in rc.d script
Hi,
This may be discussed already but I could not find which was correct,
so please point out it if we already have a consensus...
Well, I am wondering if an rc.d script installed by a port must have
": ${foo_enable:=NO}" line. An example in the porter's handbook
includes this, and I can understand it works fine. My question is
"this is really needed or not".
When $foo_enable is not defined, checkyesno() displays "WARNING:
$foo_enable is not set properly - see rc.conf(5)" and it is
interpreted as NO. I was thinking this message is useful for letting
people know which knob(s) should be configured by themselves after
the installation, but recently someone pointed out this was not
consistent and the default value should be defined as NO in the
script.
I can understand setting it as NO by default and allowing a user to
override YES/NO in rc.conf work fine and intuitive. However, is
there a case that the $foo_enable is set as YES by default? If not,
what is the reason why the warning is displayed instead of simply
thinking it as NO when $foo_enable is undefined?
My feeling is that 1) $foo_enable should be interpreted as NO if not
defined and a user should configure it (YES/NO) by herself after the
installation, and 2) other variables like $foo_flags or $foo_pidfile
should have their default values to allow the software be able to run
simply by adding a line foo_enable=YES into rc.conf.
While I do not have a strong opinion on 1), I am not sure if it is
the correct interpretation. Setting the variable as NO by default
will make the warning message disappear, but in that case it is
difficult for the user to find the knobs. And if it is equivalent to
NO when the variable is not defined, I don't understand what is the
advantage of setting it as NO explicitly by default.
Since most of ports I am maintaining do not have this line, I need to
fix them if setting the variable as NO consistently is preferable.
-- Hiroki
pgpv4P0QQ26b8.pgp
Description: PGP signature
Re: Whither Thunderbird 3.1(.1)?
On 03.08.2010 18:59, Joe Marcus Clarke wrote:
On 8/3/10 3:05 AM, Beat Gaetzi wrote:
On 03.08.2010 02:59, Doug Barton wrote:
Just curious about the status of native Thunderbird 3.1.x. IMO the linux
version is a significant improvement over 3.0.x, so I'd like to run the
native version and get out of "clunky font land" sometime soon. :) Do
y'all have a roadmap? If I missed it, my apologies ...
Thunderbird 3.1 is ready since it has been released but the update
depends on this repo-cpoy:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148136
Ugh. With all my travel and work lately, the repocopies moved to cvs so
I missed them in my weekly sweep. Sorry. I just took care of this.
Great! Thank you. I will commit Lightning 1.0b1 and Thunderbird 3.1.1
within the next hours.
Beat
Is it possible to get deskutils/lightning working with
thunderbird-3.1.1? I don't really wish to downgrade to 3.0.6.
I tried changing the Makefile to read
RUN_DEPENDS+=
${LOCALBASE}/lib/thunderbird/thunderbird-bin:${PORTSDIR}/mail/thunderbird
but it failed to build.
--
I am currently away on leave, traveling through time and will be
returning last week.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: :${foo_enable:=NO} in rc.d script
On 08/04/10 20:25, Hiroki Sato wrote:
Hi,
This may be discussed already but I could not find which was correct,
so please point out it if we already have a consensus...
Well, I am wondering if an rc.d script installed by a port must have
": ${foo_enable:=NO}" line.
That particular style is not mandated, but the policy is that all ports
should ship with a default setting of _enable=no. The default is a
security issue, in that an affirmative step by the user should be
required to enable newly installed services. This also mirrors policy
for almost everything in the base. Although in the last few years more
services in the base have defaulted to on, of the 20 or so things in
/etc/defaults/rc.conf that are enabled by default there are only 3 that
are actual services; devd, sendmail_submit, and cron. Most of the rest
are either boot-time things (like cleanvar_) or configuration elements
of services that are themselves disabled by default (like
named_chroot_autoupdate and named_symlink_enable). Requiring the
explicit setting of _enable to no (rather than letting it error out)
also mirrors the practice in the base of having /etc/defaults/rc.conf
which explicitly disables everything.
I find it impossible to believe that at this stage in the game there are
still users who are confused by how to enable services, and if they are
the example in the porter's handbook provides sample text for the
comments of the rc.d script to explain what to do. There are also a
non-zero number of ports that include instructions in their pkg-message
files.
Since most of ports I am maintaining do not have this line, I need to
fix them if setting the variable as NO consistently is preferable.
I believe the examples in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html
are fairly thorough, and relatively well documented. If you have any
questions about the text please don't hesitate to bring them up, I am
always looking for ways to improve it.
hth,
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/
Computers are useless. They can only give you answers.
-- Pablo Picasso
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Whither Thunderbird 3.1(.1)?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/04/10 08:12, Beat Gaetzi wrote: > On 03.08.2010 20:52, Doug Barton wrote: >> On 08/03/10 09:59, Joe Marcus Clarke wrote: >>> On 8/3/10 3:05 AM, Beat Gaetzi wrote: On 03.08.2010 02:59, Doug Barton wrote: > Just curious about the status of native Thunderbird 3.1.x. IMO the > linux > version is a significant improvement over 3.0.x, so I'd like to run the > native version and get out of "clunky font land" sometime soon. :) Do > y'all have a roadmap? If I missed it, my apologies ... Thunderbird 3.1 is ready since it has been released but the update depends on this repo-cpoy: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148136 >>> >>> Ugh. With all my travel and work lately, the repocopies moved to cvs so >>> I missed them in my weekly sweep. Sorry. I just took care of this. >>> >>> Joe >>> In the meantime you could use the port from our development repository: # svn co https://trillian.chruetertee.ch/svn/freebsd-gecko/trunk/mail/thunderbird >> >> Careful, if you guys start rewarding my whinging about stuff you'll just >> get more of it. :) >> >> Meanwhile, hopefully ale can coordinate with y'all on the enigmail >> plugin since they made a break on compatibility and enigmail 1.0.x only >> works with tbird <= 3.0.x, and enigmail 1.1.x only works with tbird >= >> 3.1.x. Woo hoo! > > Please take a look at this patch which updates enigmail-thunderbird to > 1.1.2 and works with Thunderbird 3.1: > http://people.freebsd.org/~beat/patches/enigmail-1.1.2.patch > > ale: Could you please consider committing this patch? This patch worked for me, thanks Beat for all your hard work on this. Doug - -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBCAAGBQJMWlZbAAoJEFzGhvEaGryEvDgH/1RI+0WkK0Oo1dDV7G/xHspm DD9OBwXJFbCJr5fWYYGuZmtPbpoqqKymZRJyLT5ZvUFCJKKFnWkg9WPzwXI1/YMx 8bVkcnSGy/mqSoaiF9N+h77B9c2CQI1WKrOuFf32XpF3pxt9Ugf6uzTY2XOShqB5 NIGhVjyOAwV1R/83Nz1R+dM7BrecPqm+4qZ1ptFY+51p9wCz0BTWP84oa4W4h6iQ c4BrfsjncW3+nFYm2CNoLbDmJl0QOsBvq0lz2P+Y29YLyDWYe9ipl8rNwsU5J/oa 1SLeGBb1m8yChNWZBw20Yy+etJPd+C157nhFNKzBvReqiZuxYfC7hok38p/poFA= =dY+X -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
