<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-forward-container">OK, I did not realize that
cyrus-devel has become cyrus-imap. Forwarding to cyrus-sasl.
Bcc'd cyrus-devel.<br>
My apologies.<br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>Hi. I have some libsasl patches and bugs, need guidance</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Mon, 12 Oct 2015 12:01:11 -0700</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Jan Parcel <a class="moz-txt-link-rfc2396E" href="mailto:jan.parcel@oracle.com"><jan.parcel@oracle.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:cyrus-devel@lists.andrew.cmu.edu">cyrus-devel@lists.andrew.cmu.edu</a>, FIVEASH
<a class="moz-txt-link-rfc2396E" href="mailto:will.fiveash@oracle.com"><will.fiveash@oracle.com></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Hi.<br>
<div class="moz-forward-container"> <br>
I am updating form 2.1.25 to 2.1.26, and I have found a few
things I had to fix for Solaris, probably most<br>
recent versions of Solaris, not just future ones. Do you have a
"how to contribute" page? I thought I had seen one but now
can't find it.<br>
<br>
I also see that you were patching things over the summer and
wondered how many of those could be considered security
vulerability fixes, especially the gssapi fixes. How long
before 2.1.27 ? What would trigger such a release?<br>
<br>
And I wondered about things I've seen in emails this summer,
regarding the imap probect wrt libsasl, such as<br>
<br>
"If you want to force TLS to be used before any SASL mechs are
advertised, set sasl_minimum_layer to 129 or higher." (We do
not use cyrus imap)<br>
<br>
Here are the bugs I wanted to file in BugZilla, I was wondering
if you covered any of these in some of your<br>
recent git integrations, I assume duplications are Not Good
(TM):<br>
<br>
sasl install dir for plugins should be separately configurable<br>
<small><i> (this is caused by the fact that something in
/usr/lib/sasl2/64/ is found in Solaris by asking for
/usr/lib/sasl2 and knowing that the caller is a 64-bit
program)</i></small><br>
<br>
libtool.m4 overrides configuration for --no-verify<br>
incorrect function definition for do_request in ipc_doors.c<br>
sasl adjustment for location of gssapi.h incorrectly implemented<br>
CMU cyrus-sasl missing man pages that we require<br>
<br>
and possibly:<br>
Moving to autotools 1.15 breaks cmu cyrus-sasl build<br>
<br>
I have patches for all of those, of course, and our preference
is for them to either go upstream or be<br>
EOL'd by fixes pulled down from upstream, preferably in a later
cyrus-sasl release such as 2.1.27.<br>
<br>
Thanks in advance for any help.<br>
<br>
Jan Parcel<br>
Software Engineer<br>
Oracle<br>
<br>
<br>
</div>
<br>
<br>
</div>
<br>
</body>
</html>