--On Monday, June 24, 2024 9:58 AM -0400 Simo Sorce wrote:
I have never seen a single deployment of krb4 in 20 years, shred it.
When I started at Stanford in 1998, we were using Krb4, but were in the
process of moving to Krb5. IIRC we stopped using it around 2003. I've
never seen anothe
I filed an issue to remove the NTLM SASL mechanism starting with Cyrus-SASL
2.2. I think the discussion on the main SASL list today furthers this as
being necessary given what Simo discussed about it being a broken custom
implementation of NTLM. Are there any objections to this?
If someone w
I've created a PR for updated release procedures for Cyrus-SASL as the
instructions in README.andrew were obsolete.
Ken and Ellie especially, please review.
Thanks!
Regards,
Quanah
--
Cyrus: Devel
Permalink:
https://cyrus.topicbox.com/groups/devel/T024
--On Tuesday, February 8, 2022 12:10 PM -0800 Quanah Gibson-Mount
wrote:
more /tmp/sphinx-err-099bk_9r.log
# Sphinx version: 1.8.5
I got it to build (although it throws tons of warnings) by upgrading to the
latest Sphinx manually, but it concerns me that we have a depdency on an
The 2.1.28 release is blocked by the fact that Cyrus-SASL was switched to
using Sphinx for building out the man pages and other documentation. This
switch has generated numerous issues in github and continues to be a
significant pain point as every release of Sphinx seems to require a
signific
--On Friday, February 4, 2022 9:49 AM +1100 ellie timoney
wrote:
One risk of having the configure script checked into the repository is
that people will misunderstand that it's generated, and spend a lot of
time manually solving some problem, only to have their PR rejected
because the chan
I'd like to check in the configure script to the repository rather than
having it be done a seperate step outside of the process. Changes to
configure are rare and generally packagers will generate their own copy
regardless of whether or not one is checked into the git repository, so it
doesn'
--On Tuesday, October 19, 2021 3:34 PM -0700 Quanah Gibson-Mount
wrote:
Cyrus-SASL 2.1.28 is ready for testing off of the cyrus-sasl-2.1 branch.
I know in the past a RC tarball was generated by Ken. I was wondering if
anyone has any documented procedure around this. I do want to be sure
--On Monday, October 25, 2021 5:51 PM + Joseph Chen
wrote:
From: Quanah Gibson-Mount
Sent: Wednesday, October 20, 2021 9:44 PM
> Thanks @Quanh! Follow your suggestions, I was able to build on Windows
> with the latest master branch, after @Alexdran's work got merged i
? My employer does not approve to include SleepyCat
or Berkeley DB at all.
Use LMDB.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
-
as
avoid shipping build time files that incorrectly ended up in the 2.1.27
release tarball.
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.
--On Wednesday, October 13, 2021 1:05 AM + Joseph Chen
wrote:
-Original Message-
From: Quanah Gibson-Mount
Sent: Tuesday, October 12, 2021 4:32 PM
joseph.c...@non.keysight.com
wrote:
>
> Hello,
>
>
>
> Can someone here tell me how to successfully bui
;
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--
Cyrus: Devel
Permalink:
https://cyrus.topicbox.com/groups/devel/
x27;t the DCO or lack of one.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--
Cyrus: Devel
Permalink:
https://cyrus.topicbox.com/g
mation on how it does (or
doesn't) affect modern OSX compilation.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--
Cyrus: Devel
Pe
st legally ensure that any
contributions are made to a project free of burden before they can be
accepted. The DCO allows this.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://
rd on SASL development and
releases. :)
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--
Cyrus: Devel
Permal
g on me at the
moment but I my paying job is currently consuming my time so that I haven't
been able to get the last portion complete.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<ht
--On Monday, February 22, 2021 3:31 PM +0200 Дилян Палаузов
wrote:
Hello,
is this "improvement" now concluded-à-la-consensus?
Yes.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenL
l
problems.
It is not a hypothetical problem. I understand you don't understand the
issues, but that doesn't mean they don't exist.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLD
in EU copyright law, for example.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--
Cyrus: Devel
Permalink:
https://cyrus.t
citly transfer
their rights to the project for their contribution. What can be done is
using something like a CLA bot so it's only necessary the first time and
all future contributions are covered unless they explicitly revoke the
authorization.
--Quanah
--
Quanah Gibson-Mount
Product Archi
ack and
contact *every person* who had ever contributed to the project to relicense
OR rip out the contribution to do their relicensing for 3.0 because they
hadn't always had a CLA/IPR process in place.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged,
lly be accepted.
-
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--
C
24 matches
Mail list logo
