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. Jus
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
e, 23 Feb 2016 18:25:05 -0800
> >>>>> Kyle Amon 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
Hi,
>>>>> On Tue, 23 Feb 2016 18:25:05 -0800
>>>>> Kyle Amon 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
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
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 someth
Hi,
>>>>> On Sat, 10 Oct 2015 08:54:05 +0900
>>>>> Hajimu UMEMOTO 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 hav
Hi,
>>>>> On Fri, 9 Oct 2015 18:57:56 +0100
>>>>> Mark Knight 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
y/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/freebs
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
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
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
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
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/
48181000 +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_
+--On 2 octobre 2015 13:13:41 +0300 Pavel Timofeev wrote:
| Good day!
Grml, looking into it.
--
Mathieu Arnold
pgphULBWf2I1T.pgp
Description: PGP signature
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:amd6
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-Chan
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 individ
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 wrote:
> Hi,
>
> > On Tue, 11 Dec 2012 05:36:48 -0600
> > Franci Nabalanci said:
>
> lumiwa> I red that k
Hi,
> On Tue, 11 Dec 2012 05:36:48 -0600
> Franci Nabalanci 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/
__
I reinstall Python 2.7
I red that kdepimlibs doesn't build too...
On Tue, Dec 11, 2012 at 5:28 AM, Franci Nabalanci 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.
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 wrote:
> Hi,
>
> > On Mon, 10 Dec 2012 16:04:56 -0600
> >>>
Hi,
> On Mon, 10 Dec 2012 16:04:56 -0600
> Franci Nabalanci 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.
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 wrote:
> I read /usr/ports/UPDATING:
>
> portmaster -r cyrus-sasl-
>
> which I did and I have ma
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:
===> Compr
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.
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, t
[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'
g already?
I've used both Dovecot and Cyrsus sasl. I would say that Dovecot sasl is much
easier to install than Cyrsu sasl. It is implemented as a daemon to which an
application communicates via a domain socket rather than as a shared library
(which is how Cyrus sasl is implemented). Becaus
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:
>>
On Wed, Apr 04, 2007 at 08:56:33AM -0500, Eric wrote:
> 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
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,
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
If you also need a POP3/IMAP server you might want to take a
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
If you also need a POP3/IMAP server you might want to take a look at
Dovecot
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
If you also need a POP3/IMAP server you might want to take a look at
Dovecot. I'm using Do
On 4/3/07, Anton Blajev <[EMAIL PROTECTED]> wrote:
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)
main
-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
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
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
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
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, cu
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 yo
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
44 matches
Mail list logo
