Re: SRP support for the cyrus-sasl-2.1.26_12 port

[Kyle Amon]

On Wed, 24 Feb 2016 23:23:42 +0900
Thus spake Hajimu UMEMOTO :

> Hi,
> 
> > On Wed, 24 Feb 2016 04:13:40 -0800
> > Kyle Amon  said:  
> 
> amonk> Awesome!  Works for me, but why not just just make the SRP and 
> SRP-SETPASS
> amonk> options off by default?  I'm quite happy either way.  Just wondering.  
> 
> Because, the feature which is off by default is not available by the
> package.  Further, the cyrus-sasl2 port has the separate ports for
> some plugins, already.
> Didn't you want to support SRP out of the box?  :-)
> 
> Sincerely,
> 
> --
> Hajimu UMEMOTO
> u...@mahoroba.org  u...@freebsd.org
> http://www.mahoroba.org/~ume/

Yeah, man.  Sweet.  Thanks. :)

--Kyle

-- 

  CA +1-778-819-UNIX  BackWatcher, Inc.
  US +1-425-584-UNIX  Information Security Solutions
 SIP am...@backwatcher.comwww.backwatcher.com

INUM +883-5100-0990-1657  /  ISN UNIX*1917  /  C*NET 1-731-UNIX

GPG ed25519/F57091DBD60FBBB8 [ed25519/D60FBBB8]
985C 5B61 4ACE C89A 0DEE  ECCD F570 91DB D60F BBB8

rsa4096/CF001165F36E1CAB [rsa4096/F36E1CAB]
6050 05B7 9FF1 CC21 3F00  CEBB CF00 1165 F36E 1CAB

OTR E1A46361 9FD0D801 0132D21A FE2E96BE 39E3F069 : am...@backwatcher.com
5AB3E0B8 31F6ADB4 9A7D2FC2 A8235281 5776701E : silcnet



pgp796ORdYLfH.pgp
Description: OpenPGP digital signature

Re: SRP support for the cyrus-sasl-2.1.26_12 port

[Hajimu UMEMOTO]

Hi,

> On Wed, 24 Feb 2016 04:13:40 -0800
> Kyle Amon  said:

amonk> Awesome!  Works for me, but why not just just make the SRP and 
SRP-SETPASS
amonk> options off by default?  I'm quite happy either way.  Just wondering.

Because, the feature which is off by default is not available by the
package.  Further, the cyrus-sasl2 port has the separate ports for
some plugins, already.
Didn't you want to support SRP out of the box?  :-)

Sincerely,

--
Hajimu UMEMOTO
u...@mahoroba.org  u...@freebsd.org
http://www.mahoroba.org/~ume/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: SRP support for the cyrus-sasl-2.1.26_12 port

[Kyle Amon]

Hajimu,

Awesome!  Works for me, but why not just just make the SRP and SRP-SETPASS
options off by default?  I'm quite happy either way.  Just wondering.

Thanks much,

--Kyle

On Wed, 24 Feb 2016 19:48:38 +0900
Thus spake Hajimu UMEMOTO <u...@freebsd.org>:

> Hi,
> 
> >>>>> On Tue, 23 Feb 2016 18:25:05 -0800
> >>>>> Kyle Amon <am...@backwatcher.com> said:  
> 
> amonk> I added support for SRP (including srp-setpass [so saslpasswd2 can
> amonk> store srp salts and verifiers in the sasl password database too, if
> amonk> so desired]) to the cyrus-sasl-2.1.26_12 port.  Two small patch files
> amonk> are attached. Please consider applying them (or something very similar)
> amonk> so that FreeBSD's cyrus-sasl port can support SRP "out of the box."
> amonk> SRP is and excellent, secure authentication method, support for it has
> amonk> long existed in cyrus-sasl, and that support should be easily 
> obtainable
> amonk> by FreeBSD's users.  Help make the net a more secure place. :)  
> 
> I've committed to add security/cyrus-sasl2-srp.
> If we have the SRP and SRP-SETPASS options enabled by default, the SRP
> salts and verifiers will be stored to the sasldb as well.
> Perhaps, it is not desired by many people.  Therefore, I made the SRP
> plugin the separate port.
> 
> Sincerely,
> 
> --
> Hajimu UMEMOTO
> u...@mahoroba.org  u...@freebsd.org
> http://www.mahoroba.org/~ume/


-- 

  CA +1-778-819-UNIX  BackWatcher, Inc.
  US +1-425-584-UNIX  Information Security Solutions
 SIP am...@backwatcher.comwww.backwatcher.com

INUM +883-5100-0990-1657  /  ISN UNIX*1917  /  C*NET 1-731-UNIX

GPG ed25519/F57091DBD60FBBB8 [ed25519/D60FBBB8]
985C 5B61 4ACE C89A 0DEE  ECCD F570 91DB D60F BBB8

rsa4096/CF001165F36E1CAB [rsa4096/F36E1CAB]
6050 05B7 9FF1 CC21 3F00  CEBB CF00 1165 F36E 1CAB

OTR E1A46361 9FD0D801 0132D21A FE2E96BE 39E3F069 : am...@backwatcher.com
5AB3E0B8 31F6ADB4 9A7D2FC2 A8235281 5776701E : silcnet



pgpiJ340ZJ8CM.pgp
Description: OpenPGP digital signature

Re: SRP support for the cyrus-sasl-2.1.26_12 port

[Hajimu UMEMOTO]

Hi,

>>>>> On Tue, 23 Feb 2016 18:25:05 -0800
>>>>> Kyle Amon <am...@backwatcher.com> said:

amonk> I added support for SRP (including srp-setpass [so saslpasswd2 can
amonk> store srp salts and verifiers in the sasl password database too, if
amonk> so desired]) to the cyrus-sasl-2.1.26_12 port.  Two small patch files
amonk> are attached. Please consider applying them (or something very similar)
amonk> so that FreeBSD's cyrus-sasl port can support SRP "out of the box."
amonk> SRP is and excellent, secure authentication method, support for it has
amonk> long existed in cyrus-sasl, and that support should be easily obtainable
amonk> by FreeBSD's users.  Help make the net a more secure place. :)

I've committed to add security/cyrus-sasl2-srp.
If we have the SRP and SRP-SETPASS options enabled by default, the SRP
salts and verifiers will be stored to the sasldb as well.
Perhaps, it is not desired by many people.  Therefore, I made the SRP
plugin the separate port.

Sincerely,

--
Hajimu UMEMOTO
u...@mahoroba.org  u...@freebsd.org
http://www.mahoroba.org/~ume/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

SRP support for the cyrus-sasl-2.1.26_12 port

[Kyle Amon]

Hi,

I added support for SRP (including srp-setpass [so saslpasswd2 can
store srp salts and verifiers in the sasl password database too, if
so desired]) to the cyrus-sasl-2.1.26_12 port.  Two small patch files
are attached. Please consider applying them (or something very similar)
so that FreeBSD's cyrus-sasl port can support SRP "out of the box."
SRP is and excellent, secure authentication method, support for it has
long existed in cyrus-sasl, and that support should be easily obtainable
by FreeBSD's users.  Help make the net a more secure place. :)

Best Regards,

--Kyle

P.S.  I'm not on the freebsd-ports mailing list, FYI.

-- 

  CA +1-778-819-UNIX  BackWatcher, Inc.
  US +1-425-584-UNIX  Information Security Solutions
 SIP am...@backwatcher.comwww.backwatcher.com

INUM +883-5100-0990-1657  /  ISN UNIX*1917  /  C*NET 1-731-UNIX

GPG ed25519/F57091DBD60FBBB8 [ed25519/D60FBBB8]
985C 5B61 4ACE C89A 0DEE  ECCD F570 91DB D60F BBB8

rsa4096/CF001165F36E1CAB [rsa4096/F36E1CAB]
6050 05B7 9FF1 CC21 3F00  CEBB CF00 1165 F36E 1CAB

OTR E1A46361 9FD0D801 0132D21A FE2E96BE 39E3F069 : am...@backwatcher.com
5AB3E0B8 31F6ADB4 9A7D2FC2 A8235281 5776701E : silcnet

--- Makefile.dist	2016-02-23 07:06:03.323811000 -0800
+++ Makefile	2016-02-23 07:22:56.047782000 -0800
@@ -40,13 +40,13 @@
 
 NO_OPTIONS_SORT=	yes
 OPTIONS_DEFINE=		ALWAYSTRUE AUTHDAEMOND DOCS KEEP_DB_OPEN \
-			OBSOLETE_CRAM_ATTR BDB MYSQL PGSQL
+			OBSOLETE_CRAM_ATTR BDB MYSQL PGSQL SRP-SETPASS
 OPTIONS_RADIO=		SQLITE
 OPTIONS_RADIO_SQLITE=	SQLITE2 SQLITE3
 OPTIONS_GROUP=		MECH
-OPTIONS_GROUP_MECH=	CRAM DIGEST LOGIN NTLM OTP PLAIN SCRAM
+OPTIONS_GROUP_MECH=	CRAM DIGEST LOGIN NTLM OTP PLAIN SCRAM SRP
 OPTIONS_DEFAULT=	AUTHDAEMOND OBSOLETE_CRAM_ATTR CRAM DIGEST \
-			LOGIN NTLM OTP PLAIN SCRAM
+			LOGIN NTLM OTP PLAIN SCRAM SRP SRP-SETPASS
 OPTIONS_SUB=		yes
 ALWAYSTRUE_DESC=	the alwaystrue password verifier
 ALWAYSTRUE_CONFIGURE_ENABLE=alwaystrue
@@ -90,6 +90,10 @@
 PLAIN_CONFIGURE_ENABLE=	plain
 SCRAM_DESC=		SCRAM authentication
 SCRAM_CONFIGURE_ENABLE=	scram
+SRP_DESC=		SRP authentication
+SRP_CONFIGURE_ENABLE=	srp
+SRP-SETPASS_DESC=	enable srp-setpass
+SRP-SETPASS_CONFIGURE_ENABLE=	srp-setpass
 
 .include 
 
--- pkg-plist.dist	2016-02-23 08:01:04.58401 -0800
+++ pkg-plist	2016-02-23 07:45:31.537829000 -0800
@@ -55,6 +55,11 @@
 %%PLAIN%%lib/sasl2/libplain.so
 %%PLAIN%%lib/sasl2/libplain.so.3
 %%PLAIN%%lib/sasl2/libplain.so.3.0.0
+%%SRP%%lib/sasl2/libsrp.a
+%%SRP%%lib/sasl2/libsrp.la
+%%SRP%%lib/sasl2/libsrp.so
+%%SRP%%lib/sasl2/libsrp.so.3
+%%SRP%%lib/sasl2/libsrp.so.3.0.0
 lib/sasl2/libsasldb.a
 lib/sasl2/libsasldb.la
 lib/sasl2/libsasldb.so


pgpa01Oaz9HnD.pgp
Description: OpenPGP digital signature

FreeBSD Port: subversion-1.9.3_1 cyrus-sasl-saslauthd-2.1.26_3

[Joseph Bruni]

Hello,

I recently struggled with getting subversion with SASL to work with LDAP 
authentication on freebsd 10.2. Both subversion (1.9.3) and SASL (2.1.26) were 
install from ports.

For the most part configuration followed the documentation, but there was one 
hitch. I'm not sure if this is something that should be handled as part of the 
subversion port or as part of the SASL port.

When subversion is installed, the default rc scripts run svnserve with a 
user/group of svn/svn. However, when SASL-authd is installed, it uses a domain 
socket path of /var/run/saslauthd with ownership of cyrus/mail. This directory 
is not readable by the svn user.

To make this work, I either had to add the svn user to the "mail" group, or 
relax the permisson on /var/run/saslauthd so that svnserve would be able to 
open the socket to the saslauthd. Perhaps the permissions to the socket were 
too restrictive by default.

Regards,
Joseph



smime.p7s
Description: S/MIME cryptographic signature

Re: cyrus-sasl-saslauthd won't build anymore

[Hajimu UMEMOTO]

Hi,

>>>>> On Sat, 10 Oct 2015 08:54:05 +0900
>>>>> Hajimu UMEMOTO <u...@freebsd.org> said:

lists> So it looks like there's a conflict between the current versions of
lists> security/krb5 and security/cyrus-sasl-saslauthd.

ume> It is not so easy.  It seems you have openssl port installed as well.
ume> Since search path of include file is same between openssl port and mit
ume> kerberos, it seems impossible to build with openssl port and base
ume> heimdal when mit kerberos is installed without support of ports
ume> framework for gssapi and/or openssl.

I could build cyrus-sasl2-saslauthd with openssl port and base heimdal
even when mit kerberos is installed, with the attached patch applied.
However, it links two shared version of licrypto like follows:

$ ldd work/cyrus-sasl-2.1.26/saslauthd/saslauthd | grep -E '(gss|krb|crypto)'
libgssapi.so.10 => /usr/lib/libgssapi.so.10 (0x80082d000)
libgssapi_krb5.so.10 => /usr/lib/libgssapi_krb5.so.10 (0x800a36000)
libkrb5.so.11 => /usr/lib/libkrb5.so.11 (0x800e5a000)
libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x80151e000)
libcrypto.so.7 => /lib/libcrypto.so.7 (0x802c01000)

One comes from base heimdal and the another comes from openssl port. I
suspect such binary is usable.

Sincerely,

Index: security/cyrus-sasl2-saslauthd/Makefile
===
--- security/cyrus-sasl2-saslauthd/Makefile	(revision 398984)
+++ security/cyrus-sasl2-saslauthd/Makefile	(working copy)
@@ -92,7 +92,8 @@
 .if ${OPENSSLBASE} == /usr
 CONFIGURE_ARGS+=--with-openssl=yes
 .else
-CONFIGURE_ARGS+=--with-openssl=${OPENSSLBASE}
+WRKOPENSSLBASE=	${WRKDIR}/openssl
+CONFIGURE_ARGS+=--with-openssl=${WRKOPENSSLBASE}
 .endif
 
 SASLAUTHD_RUNPATH?=	/var/run/saslauthd
@@ -110,6 +111,14 @@
 
 SUB_LIST+=	SASLAUTHD_RUNPATH=${SASLAUTHD_RUNPATH}
 
+.if ${OPENSSLBASE} != /usr
+pre-configure:
+	${MKDIR} ${WRKOPENSSLBASE}/include ${WRKOPENSSLBASE}/lib
+	${LN} -s ${OPENSSLBASE}/include/openssl ${WRKOPENSSLBASE}/include
+	${LN} -s ${OPENSSLBASE}/lib/libcrypto.* ${OPENSSLBASE}/lib/libssl.* \
+		${WRKOPENSSLBASE}/lib
+.endif
+
 do-build:
 	cd ${WRKSRC}/include && ${MAKE}
 	cd ${WRKSRC}/sasldb && ${MAKE}

--
Hajimu UMEMOTO
u...@mahoroba.org  u...@freebsd.org
http://www.mahoroba.org/~ume/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: cyrus-sasl-saslauthd won't build anymore

[Hajimu UMEMOTO]

Hi,

>>>>> On Fri, 9 Oct 2015 18:57:56 +0100
>>>>> Mark Knight <li...@knigma.org> said:

lists> Mine didn't. In the end, my workaround was to uninstall security/krb5

lists> So it looks like there's a conflict between the current versions of
lists> security/krb5 and security/cyrus-sasl-saslauthd.

It is not so easy.  It seems you have openssl port installed as well.
Since search path of include file is same between openssl port and mit
kerberos, it seems impossible to build with openssl port and base
heimdal when mit kerberos is installed without support of ports
framework for gssapi and/or openssl.

Sincerely,

--
Hajimu UMEMOTO
u...@mahoroba.org  u...@freebsd.org
http://www.mahoroba.org/~ume/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: cyrus-sasl-saslauthd won't build anymore

[Mark Knight]

On 06/10/2015 04:17, Walter Schwarzenfeld wrote:

Try to compile it in the port not with portupgrade. (For me in the port
compiles fine.)


Mine didn't. In the end, my workaround was to uninstall security/krb5

So it looks like there's a conflict between the current versions of 
security/krb5 and security/cyrus-sasl-saslauthd.


Cheers, Mark

--
Mark Knight
Mobile: +44 7753 250584.  http://www.knigma.org/
Email: ma...@knigma.org.  Skype: knigma
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: cyrus-sasl-saslauthd won't build anymore

[Mark Knight]

On 03/10/2015 16:33, Mark Knight wrote:

Sorry, my mail was confusing. I current have these installed:

 cyrus-sasl-2.1.26_12
 cyrus-sasl-saslauthd-2.1.26_1

Updating to cyrus-sasl-saslauthd-2.1.26_3 is refusing to build, per the
log:

 http://www.knigma.org/scratch/cyrus-sasl-saslauthd.txt


Any ideas on this one please? This has been broken for a few days now. 
All my other ports are up-to-date and there's nothing obvious in 
/usr/ports/UPDATING.


Does this build for others?

Thanks, Mark
--
Mark Knight
Mobile: +44 7753 250584.  http://www.knigma.org/
Email: ma...@knigma.org.  Skype: knigma
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: cyrus-sasl-saslauthd won't build anymore

[Walter Schwarzenfeld]

Try to compile it in the port not with portupgrade. (For me in the port
compiles fine.)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: cyrus-sasl-saslauthd won't build anymore

[Matthew Seaman]

On 03/10/2015 14:46, Mark Knight wrote:
> Is anyone else having issues building:
> 
>     cyrus-sasl-saslauthd-2.1.26_1
> 
> cyrus-sasl-2.1.26_12 is building okay, and I've tried re-building all
> dependencies and checking UPDATING. I'm on FreeBSD 10.2-RELEASE-p3

That update was backed out after it was found not to work.  Update your
ports -- you should find cyrus-sasl-saslauthd-2.1.26_2 now.

Cheers,

Matthew





signature.asc
Description: OpenPGP digital signature

cyrus-sasl-saslauthd won't build anymore

[Mark Knight]

Is anyone else having issues building:

cyrus-sasl-saslauthd-2.1.26_1

cyrus-sasl-2.1.26_12 is building okay, and I've tried re-building all 
dependencies and checking UPDATING. I'm on FreeBSD 10.2-RELEASE-p3


Full build log here:

http://www.knigma.org/scratch/cyrus-sasl-saslauthd.txt

Thanks for any ideas!
--
Mark Knight
Mobile: +44 7753 250584.  http://www.knigma.org/
Email: ma...@knigma.org.  Skype: knigma
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: cyrus-sasl-saslauthd won't build anymore

[Mark Knight]

On 03/10/2015 14:32, Matthew Seaman wrote:

That update was backed out after it was found not to work.  Update your
ports -- you should find cyrus-sasl-saslauthd-2.1.26_2 now.


Sorry, my mail was confusing. I current have these installed:

cyrus-sasl-2.1.26_12
cyrus-sasl-saslauthd-2.1.26_1

Updating to cyrus-sasl-saslauthd-2.1.26_3 is refusing to build, per the log:

http://www.knigma.org/scratch/cyrus-sasl-saslauthd.txt

--
Mark Knight
Mobile: +44 7753 250584.  http://www.knigma.org/
Email: ma...@knigma.org.  Skype: knigma
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: can't compile net/openldap24-server after last cyrus-sasl* upgrade

[Mathieu Arnold]

+--On 2 octobre 2015 13:13:41 +0300 Pavel Timofeev  wrote:
| Good day!

Grml, looking into it.

-- 
Mathieu Arnold

pgphULBWf2I1T.pgp
Description: PGP signature

can't compile net/openldap24-server after last cyrus-sasl* upgrade

[Pavel Timofeev]

Good day!

It fails, here is poudriere log.
...
===
===>   openldap-sasl-server-2.4.42_2 depends on package:
cyrus-sasl-gssapi>0 - not found
===>   Installing existing package /packages/All/cyrus-sasl2-gssapi-2.1.26_4.txz
[FreeBSD:10:amd64-default-job-01] Installing cyrus-sasl2-gssapi-2.1.26_4...
[FreeBSD:10:amd64-default-job-01] Extracting
cyrus-sasl2-gssapi-2.1.26_4: ... done
===>   openldap-sasl-server-2.4.42_2 depends on package:
cyrus-sasl-gssapi>0 - not found
*** Error code 1

Stop.
make: stopped in /usr/ports/net/openldap24-server
>> Cleaning up wrkdir
===>  Cleaning for openldap-sasl-server-2.4.42_2
build of net/openldap24-server ended at Fri Oct  2 13:03:00 MSK 2015
build time: 00:02:07
!!! build failure encountered !!!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: can't compile net/openldap24-server after last cyrus-sasl* upgrade

[Pavel Timofeev]

2015-10-02 13:25 GMT+03:00 Mathieu Arnold <m...@freebsd.org>:
>
>
> +--On 2 octobre 2015 13:13:41 +0300 Pavel Timofeev <tim...@gmail.com> wrote:
> | Good day!
>
> Grml, looking into it.
>
> --
> Mathieu Arnold

root@pyxis-v# diff -u Makefile.orig Makefile

--- Makefile.orig   2015-10-02 17:55:19.948181000 +0300
+++ Makefile2015-10-02 13:17:14.52799 +0300
@@ -156,7 +156,7 @@
 CONFLICTS= ${PKGNAMEPREFIX}${PORTNAME}-client-2.*
 PKGNAMESUFFIX= -sasl-server
 .if ${PORT_OPTIONS:MGSSAPI}
-RUN_DEPENDS+=
cyrus-sasl-gssapi>0:${PORTSDIR}/security/cyrus-sasl2-gssapi
+RUN_DEPENDS+=
cyrus-sasl2-gssapi>0:${PORTSDIR}/security/cyrus-sasl2-gssapi
 .endif
 .else
 CONFLICTS= ${PKGNAMEPREFIX}${PORTNAME}-sasl-client-2.*


Seems like it helped me.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ports/174308: security/cyrus-sasl2: cyrus-sasl-2.1.25_2 will not compile with PostgreSQL 9.1.3

[ume]

Synopsis: security/cyrus-sasl2: cyrus-sasl-2.1.25_2 will not compile with 
PostgreSQL 9.1.3

Responsible-Changed-From-To: ume-ports
Responsible-Changed-By: ume
Responsible-Changed-When: Wed Dec 12 15:18:18 UTC 2012
Responsible-Changed-Why: 
It seems to me that this issue is not for individual ports such as
cyrus-sasl2, but for VALID_PGSQL_VER in bsd.databases.mk.

http://www.freebsd.org/cgi/query-pr.cgi?pr=174308
___
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: ports/174308: [bsd.database.mk] cyrus-sasl-2.1.25_2 will not compile with PostgreSQL 9.1.3

[linimon]

Old Synopsis: security/cyrus-sasl2: cyrus-sasl-2.1.25_2 will not compile with 
PostgreSQL 9.1.3
New Synopsis: [bsd.database.mk] cyrus-sasl-2.1.25_2 will not compile with 
PostgreSQL 9.1.3

Responsible-Changed-From-To: ports-freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Dec 12 15:35:16 UTC 2012
Responsible-Changed-Why: 
reassign.

http://www.freebsd.org/cgi/query-pr.cgi?pr=174308
___
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: cyrus-sasl

[Franci Nabalanci]

Thank you...looks like that I am a genie pig :).

It stopped again because gobject-introspection looks for python 2.7 but I
use 2.5 all the time and didn't complain...

Don't worry...

On Mon, Dec 10, 2012 at 11:49 PM, Hajimu UMEMOTO u...@freebsd.org wrote:

 Hi,

  On Mon, 10 Dec 2012 16:04:56 -0600
  Franci Nabalanci lum...@gmail.com said:

 lumiwa === gconf2-2.32.0_3 cannot install: unknown OpenLDAP version:
 Shared
 lumiwa object libsasl2.so.2 not found, required by ldapwhoami.
 lumiwa *** [all] Error code 1

 It seems we cannot remove old lib (libsasl2.so.2) during upgrade.
 I've just committed to change UPDATING to recommend to use -w option
 of portmaster.

 Sincerely,

 --
 Hajimu UMEMOTO
 u...@mahoroba.org  ume@{,jp.}FreeBSD.org
 http://www.mahoroba.org/~ume/

___
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: cyrus-sasl

[Franci Nabalanci]

I reinstall Python 2.7

I red that kdepimlibs doesn't build too...

On Tue, Dec 11, 2012 at 5:28 AM, Franci Nabalanci lum...@gmail.com wrote:

 Thank you...looks like that I am a genie pig :).

 It stopped again because gobject-introspection looks for python 2.7 but I
 use 2.5 all the time and didn't complain...

 Don't worry...

 On Mon, Dec 10, 2012 at 11:49 PM, Hajimu UMEMOTO u...@freebsd.org wrote:

 Hi,

  On Mon, 10 Dec 2012 16:04:56 -0600
  Franci Nabalanci lum...@gmail.com said:

 lumiwa === gconf2-2.32.0_3 cannot install: unknown OpenLDAP version:
 Shared
 lumiwa object libsasl2.so.2 not found, required by ldapwhoami.
 lumiwa *** [all] Error code 1

 It seems we cannot remove old lib (libsasl2.so.2) during upgrade.
 I've just committed to change UPDATING to recommend to use -w option
 of portmaster.

 Sincerely,

 --
 Hajimu UMEMOTO
 u...@mahoroba.org  ume@{,jp.}FreeBSD.org
 http://www.mahoroba.org/~ume/



___
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: cyrus-sasl

[Hajimu UMEMOTO]

Hi,

 On Tue, 11 Dec 2012 05:36:48 -0600
 Franci Nabalanci lum...@gmail.com said:

lumiwa I red that kdepimlibs doesn't build too...

I've committed the fix to this issue.  Please try the latest one.

Sincerely,

--
Hajimu UMEMOTO
u...@mahoroba.org  ume@{,jp.}FreeBSD.org
http://www.mahoroba.org/~ume/
___
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: cyrus-sasl

[Franci Nabalanci]

It is long way to kdepimlibs...it stopped in avahi-app related with
pcrelibs.so.1 as my wife told me by phone. I am not at home yet.


On Tue, Dec 11, 2012 at 7:28 AM, Hajimu UMEMOTO u...@freebsd.org wrote:

 Hi,

  On Tue, 11 Dec 2012 05:36:48 -0600
  Franci Nabalanci lum...@gmail.com said:

 lumiwa I red that kdepimlibs doesn't build too...

 I've committed the fix to this issue.  Please try the latest one.

 Sincerely,

 --
 Hajimu UMEMOTO
 u...@mahoroba.org  ume@{,jp.}FreeBSD.org
 http://www.mahoroba.org/~ume/

___
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

cyrus-sasl

[Franci Nabalanci]

I read /usr/ports/UPDATING:

portmaster -r cyrus-sasl-

which I did and I have many problems now because update don't going nowhere
and I don't know how to save a problem(s).
My system is FreeBSD 9.1-RC3 #0 r242324. I tried with clang and gcc but the
problem is the same:


=== Compressing manual pages for cyrus-sasl-2.1.26
=== Running ldconfig
/sbin/ldconfig -m /usr/local/lib
=== Registering installation for cyrus-sasl-2.1.26
pkg: lstat(/usr/local/libdata/pkgconfig/libsasl2.pc): No such file or
directory
Installing cyrus-sasl-2.1.26... done

=== Re-installation of cyrus-sasl-2.1.26 succeeded


=== Updating ports that depend on cyrus-sasl-2.1.26

=== Launching child to update bluefish-2.2.2_1 to bluefish-2.2.2_2

=== Updating dependent ports  bluefish-2.2.2_1 (1/100)

=== Currently installed version: bluefish-2.2.2_1
=== Port directory: /usr/ports/www/bluefish

=== Starting check for build dependencies
=== Gathering dependency list for www/bluefish from ports
=== Launching child to reinstall gucharmap-2.32.1_1

=== Updating dependent ports  gucharmap-2.32.1_1 (2/100)

=== Currently installed version: gucharmap-2.32.1_1
=== Port directory: /usr/ports/deskutils/gucharmap

=== Starting check for build dependencies
=== Gathering dependency list for deskutils/gucharmap from ports
=== Launching child to reinstall gconf2-2.32.0_3

=== Updating dependent ports  gucharmap-2.32.1_1  gconf2-2.32.0_3
(3/100)

=== Currently installed version: gconf2-2.32.0_3
=== Port directory: /usr/ports/devel/gconf2

=== Starting check for build dependencies
=== Gathering dependency list for devel/gconf2 from ports
=== Dependency check complete for devel/gconf2

=== Updating dependent ports  gucharmap-2.32.1_1  gconf2-2.32.0_3
(3/100)

=== Cleaning for gconf2-2.32.0_3
=== gconf2-2.32.0_3 cannot install: unknown OpenLDAP version: Shared
object libsasl2.so.2 not found, required by ldapwhoami.
*** [all] Error code 1

Stop in /usr/ports/devel/gconf2.

=== make failed for devel/gconf2
=== Aborting update

=== Update for gconf2-2.32.0_3 failed
=== Aborting update

=== Update for gucharmap-2.32.1_1 failed
=== Aborting update

=== Update for bluefish-2.2.2_1 failed
=== Aborting update

Terminated
=== There are messages from installed ports to display,
but first take a moment to review the error messages
above. Then press Enter when ready to proceed.

Thank in advance.
___
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: cyrus-sasl

[Franci Nabalanci]

Solved:

uninstall openldap24-sasl-client
install openldap24-client
reinstall perl-XML-Parser

...and looks like it works for now...


On Mon, Dec 10, 2012 at 4:04 PM, Franci Nabalanci lum...@gmail.com wrote:

 I read /usr/ports/UPDATING:

 portmaster -r cyrus-sasl-

 which I did and I have many problems now because update don't going
 nowhere and I don't know how to save a problem(s).
 My system is FreeBSD 9.1-RC3 #0 r242324. I tried with clang and gcc but
 the problem is the same:


 === Compressing manual pages for cyrus-sasl-2.1.26
 === Running ldconfig
 /sbin/ldconfig -m /usr/local/lib
 === Registering installation for cyrus-sasl-2.1.26
 pkg: lstat(/usr/local/libdata/pkgconfig/libsasl2.pc): No such file or
 directory
 Installing cyrus-sasl-2.1.26... done

 === Re-installation of cyrus-sasl-2.1.26 succeeded


 === Updating ports that depend on cyrus-sasl-2.1.26

 === Launching child to update bluefish-2.2.2_1 to bluefish-2.2.2_2

 === Updating dependent ports  bluefish-2.2.2_1 (1/100)

 === Currently installed version: bluefish-2.2.2_1
 === Port directory: /usr/ports/www/bluefish

 === Starting check for build dependencies
 === Gathering dependency list for www/bluefish from ports
 === Launching child to reinstall gucharmap-2.32.1_1

 === Updating dependent ports  gucharmap-2.32.1_1 (2/100)

 === Currently installed version: gucharmap-2.32.1_1
 === Port directory: /usr/ports/deskutils/gucharmap

 === Starting check for build dependencies
 === Gathering dependency list for deskutils/gucharmap from ports
 === Launching child to reinstall gconf2-2.32.0_3

 === Updating dependent ports  gucharmap-2.32.1_1  gconf2-2.32.0_3
 (3/100)

 === Currently installed version: gconf2-2.32.0_3
 === Port directory: /usr/ports/devel/gconf2

 === Starting check for build dependencies
 === Gathering dependency list for devel/gconf2 from ports
 === Dependency check complete for devel/gconf2

 === Updating dependent ports  gucharmap-2.32.1_1  gconf2-2.32.0_3
 (3/100)

 === Cleaning for gconf2-2.32.0_3
 === gconf2-2.32.0_3 cannot install: unknown OpenLDAP version: Shared
 object libsasl2.so.2 not found, required by ldapwhoami.
 *** [all] Error code 1

 Stop in /usr/ports/devel/gconf2.

 === make failed for devel/gconf2
 === Aborting update

 === Update for gconf2-2.32.0_3 failed
 === Aborting update

 === Update for gucharmap-2.32.1_1 failed
 === Aborting update

 === Update for bluefish-2.2.2_1 failed
 === Aborting update

 Terminated
 === There are messages from installed ports to display,
 but first take a moment to review the error messages
 above. Then press Enter when ready to proceed.

 Thank in advance.


___
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: cyrus-sasl

[Hajimu UMEMOTO]

Hi,

 On Mon, 10 Dec 2012 16:04:56 -0600
 Franci Nabalanci lum...@gmail.com said:

lumiwa === gconf2-2.32.0_3 cannot install: unknown OpenLDAP version: Shared
lumiwa object libsasl2.so.2 not found, required by ldapwhoami.
lumiwa *** [all] Error code 1

It seems we cannot remove old lib (libsasl2.so.2) during upgrade.
I've just committed to change UPDATING to recommend to use -w option
of portmaster.

Sincerely,

--
Hajimu UMEMOTO
u...@mahoroba.org  ume@{,jp.}FreeBSD.org
http://www.mahoroba.org/~ume/
___
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

Annoying cyrus-sasl messages

[Andrea Venturoli]

It's not at all critical, but I thought I'd report that we seem to be 
hit by this too:



http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/827151


Don't know if this is a bug or feature or whether it should be turned 
upstream.


 bye
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

Re: HEADSUP: removing the old cyrus-sasl port

[Udo Schweigert]

On Fri, Mar 30, 2007 at 19:05:17 +0200, Gabor Kovesdan wrote:
  Dear Port Maintainers,
 
  I would like to inform you that the security/cyrus-sasl port is deprecated 
  and expired. It is pretty old and not really supported any more. The only 
  barrier to remove it is, that it has some dependant ports, currently the 
  following ones:
 
  databases/cyrus-smlacapd
  japanese/mutt
  japanese/mutt-devel
  mail/exim
  mail/mutt
  mail/postfix
  mail/postfix-current
  mail/postfix1
  mail/sendmail
  www/mod_auth_pwcheck
 
  Could you please modify your ports to use cyrus-sasl2 instead or remove the 
  support for the old cyrus-sasl port, please?

mail/mutt is fixed by ports/112076 (SASL-support removed).

Udo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: HEADSUP: removing the old cyrus-sasl port

[SHIOZAKI Takehiko]

[On Mar 31, Gabor Kovesdan [EMAIL PROTECTED] wrote:]

Yes, it's definitely a good idea. I think we can repo-copy cyrus-sasl2 
to cyrus-sasl as Grog mentioned, and handle the knobs after maintainers 
removed the references to the old cyrus-sasl for their ports. I'm not 
sure, if the new version is completely compatible with the old one, and 
there are ports that support both ones, so we should make sure first if 
all ports work with cyrus-sasl2, that's why I sent this headsup.

Unfortunately, SASL1 and SASL2 seem incompatible.
For example, the numbers of parameters of sasl_client_start and
sasl_decode64 are changed in SASL2 as described in
/usr/local/share/doc/cyrus-sasl2/html/appconvert.html.

-- 
SHIOZAKI Takehiko
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: cyrus-sasl alternative?

[Eric]

Jona Joachim wrote:

Anton Blajev a écrit :

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello group,
what alternative can I use insted of the port scheduled for deletion:

portname:   security/cyrus-sasl

snip

If you also need a POP3/IMAP server you might want to take a look at 
Dovecot. I'm using Dovecot SASL.


maybe i missed something, but whats wrong with the sasl2 port? isnt that 
what most people are using already?

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: cyrus-sasl alternative?

[Jona Joachim]

Eric a écrit :

Jona Joachim wrote:

Anton Blajev a écrit :

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello group,
what alternative can I use insted of the port scheduled for deletion:

portname:   security/cyrus-sasl

snip

If you also need a POP3/IMAP server you might want to take a look at 
Dovecot. I'm using Dovecot SASL.


maybe i missed something, but whats wrong with the sasl2 port? isnt that 
what most people are using already?


No there's nothing wrong with it. Anton Blajev asked about an 
alternative to security/cyrus-sasl. I like Dovecot very much so I wanted 
to mention it. rafan already mentioned cyrus-sasl2 so I didn't have to 
talk about it anymore. Dovecot SASL is easier to configure than Cyrus 
SASL IMO and I know that Dovecot developers focus very much on security 
whereas for Cyrus developers I don't know. However if you prefer Cyrus I 
don't think there is anything wrong with it.


Regards, Jona
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: cyrus-sasl alternative?

[Robert Huff]

Eric writes:

  maybe i missed something, but whats wrong with the sasl2 port?
  isnt that what most people are using already?

A proposal is under serious consideration to retire cyrus-sasl
in favor of cyrus-sasl2.  -sasl is, if I remember the discussion, no
longer maintained, and is required (as opposed to supported) by very
few ports.


Robert Huff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: cyrus-sasl alternative?

[Anton - Valqk]

Thanks a lot for the tip,
I'll investigate dovecot...

Jona Joachim wrote:
 Anton Blajev a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hello group,
 what alternative can I use insted of the port scheduled for deletion:

 portname:   security/cyrus-sasl
 snip

 If you also need a POP3/IMAP server you might want to take a look at
 Dovecot. I'm using Dovecot SASL. I works flawlessly and is very easy
 to set up. I'm using it on an OpenBSD box and it works very well with
 BSD Auth. It should work just as well with PAM. The integration into
 Postfix was very easy. However if you don't need a POP3/IMAP server it
 might be overkill to install Dovecot just for SASL.
 There is also GNU SASL in the ports (security/gsasl). However I never
 used it.

 Best regards,
 Jona
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to [EMAIL PROTECTED]



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

cyrus-sasl alternative?

[Anton Blajev]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello group,
what alternative can I use insted of the port scheduled for deletion:

portname:   security/cyrus-sasl
description:RFC  SASL (Simple Authentication and Security
Layer)
maintainer: [EMAIL PROTECTED]
deprecated because: patches are unfetchable and this software is
unsupported
expiration date:2007-01-02
build errors:   none.
overview:  
http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=cyrus-sasl


I'm integrating it with postfix.
Any tips and ideas please.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGEhe3zpU6eaWiiWgRAqprAJ4hUq4iBwgbY2iLMVkvX+TDXj6LKgCeJY6R
vO5eTTeL54lIt2r/s4qbUj4=
=CSah
-END PGP SIGNATURE-

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: HEADSUP: removing the old cyrus-sasl port

[Gerhard Gonter]

Gabor Kovesdan wrote:

Dear Port Maintainers,

I would like to inform you that the security/cyrus-sasl port is 
deprecated and expired. It is pretty old and not really supported any 
more. The only barrier to remove it is, that it has some dependant 
ports, currently the following ones:


databases/cyrus-smlacapd


Please remove cyrus-smlacapd from the ports system, I doubt there
are (m)any users at all of it right now.

GG

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: HEADSUP: removing the old cyrus-sasl port

[Gabor Kovesdan]

Gerhard Gonter schrieb:

Gabor Kovesdan wrote:

Dear Port Maintainers,

I would like to inform you that the security/cyrus-sasl port is 
deprecated and expired. It is pretty old and not really supported any 
more. The only barrier to remove it is, that it has some dependant 
ports, currently the following ones:


databases/cyrus-smlacapd


Please remove cyrus-smlacapd from the ports system, I doubt there
are (m)any users at all of it right now.

Thanks, I marked it as DEPRECATED with an EXPIRATION_DATE of one week, 
so that one can notice the scheduled removal.


Regards,
Gabor
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: HEADSUP: removing the old cyrus-sasl port

[Ulrich Spoerlein]

Gabor Kovesdan wrote:
 Dear Port Maintainers,
 
 I would like to inform you that the security/cyrus-sasl port is deprecated 
 and expired. It is 
 pretty old and not really supported any more. The only barrier to remove it 
 is, that it has 
 some dependant ports, currently the following ones:
 
 databases/cyrus-smlacapd
 japanese/mutt
 japanese/mutt-devel
 mail/exim
 mail/mutt
 mail/postfix
 mail/postfix-current
 mail/postfix1
 mail/sendmail
 www/mod_auth_pwcheck
 
 Could you please modify your ports to use cyrus-sasl2 instead or remove the 
 support for the 
 old cyrus-sasl port, please?

While your at it, it would be nice if the WITH_SASL and WITH_SASL2 knobs
would be unified. Some ports interpret WITH_SASL as 'link against
libsasl2', while others (those listed above?) interpret it as 'link
against libsasl'

I think it was openldap vs postfix, where I found out about this. It
makes it unnecessary hard to use one common var in /etc/make.conf for
SASL2 support.

Thanks,
Ulrich Spoerlein
-- 
The trouble with the dictionary is you have to know how the word is
spelled before you can look it up to see how it is spelled.
-- Will Cuppy
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: HEADSUP: removing the old cyrus-sasl port

[Gabor Kovesdan]

Ulrich Spoerlein schrieb:


While your at it, it would be nice if the WITH_SASL and WITH_SASL2 knobs
would be unified. Some ports interpret WITH_SASL as 'link against
libsasl2', while others (those listed above?) interpret it as 'link
against libsasl'

I think it was openldap vs postfix, where I found out about this. It
makes it unnecessary hard to use one common var in /etc/make.conf for
SASL2 support.

Thanks,
Ulrich Spoerlein
  


Yes, it's definitely a good idea. I think we can repo-copy cyrus-sasl2 
to cyrus-sasl as Grog mentioned, and handle the knobs after maintainers 
removed the references to the old cyrus-sasl for their ports. I'm not 
sure, if the new version is completely compatible with the old one, and 
there are ports that support both ones, so we should make sure first if 
all ports work with cyrus-sasl2, that's why I sent this headsup.



Gabor
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

HEADSUP: removing the old cyrus-sasl port

[Gabor Kovesdan]

Dear Port Maintainers,

I would like to inform you that the security/cyrus-sasl port is 
deprecated and expired. It is pretty old and not really supported any 
more. The only barrier to remove it is, that it has some dependant 
ports, currently the following ones:


databases/cyrus-smlacapd
japanese/mutt
japanese/mutt-devel
mail/exim
mail/mutt
mail/postfix
mail/postfix-current
mail/postfix1
mail/sendmail
www/mod_auth_pwcheck

Could you please modify your ports to use cyrus-sasl2 instead or remove 
the support for the old cyrus-sasl port, please?


Thanks in advance,
Gabor
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: HEADSUP: removing the old cyrus-sasl port

[Greg 'groggy' Lehey]

On Friday, 30 March 2007 at 19:05:17 +0200, Gabor Kovesdan wrote:
 Dear Port Maintainers,

 I would like to inform you that the security/cyrus-sasl port is
 deprecated and expired. It is pretty old and not really supported any
 more. ...

 Could you please modify your ports to use cyrus-sasl2 instead or
 remove the support for the old cyrus-sasl port, please?

Is it really necessary to maintain the name cyrus-sasl2 for the
current port?  I'd much rather see it renamed cyrus-sasl.

Greg
--
See complete headers for address and phone numbers.


pgpq2RN58peRK.pgp
Description: PGP signature