<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.comp.encryption.gpg.gnutls.devel">
    <title>gmane.comp.encryption.gpg.gnutls.devel</title>
    <link>http://blog.gmane.org/gmane.comp.encryption.gpg.gnutls.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2995"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2987"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2985"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2980"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2977"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2972"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2963"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2960"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2952"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2951"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2949"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2948"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2947"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2944"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2938"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2934"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2928"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2926"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2917"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2912"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2995">
    <title>GnuTLS 2.5.4</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2995</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Simon Josefsson</dc:creator>
    <dc:date>2008-08-18T23:07:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2987">
    <title>GnuTLS 2.5.3</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2987</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Simon Josefsson</dc:creator>
    <dc:date>2008-08-14T08:37:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2985">
    <title>more on read_s2k() for GnuTLS 2.4.1 (including "GNU dummy S2K")</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2985</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Daniel Kahn Gillmor</dc:creator>
    <dc:date>2008-08-14T02:15:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2980">
    <title>TLS over SCTP</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2980</link>
    <description>Hello,    [sorry to reposting on the same topic as in help-gnutls, but 
the content is slightly different]

I am wanting to use the gnutls library to achieve TLS over a 
multi-stream SCTP connection, as detailed in RFC 3436. Unfortunately it 
seems that the current support in gnutls for providing custom transport 
functions is not sufficient to achieve this.

For people who are not familiar with SCTP, I'll now give a short 
introduction on this protocol. SCTP is a reliable transport protocol (as 
TCP), message-oriented (as UDP), which provides the capability to create 
multiple streams inside one connection. The messages in one stream are 
ordered, but each stream is independent from the others. This allows (in 
some applications) to avoid head-of-the-line blocking problem that 
occurs in TCP when some data is lost during a transmission. SCTP also 
provides other interesting features such as support for multihoming. On 
an API point of view, one socket object is created, and the number of 
streams is negotia</description>
    <dc:creator>Sebastien Decugis</dc:creator>
    <dc:date>2008-08-01T05:26:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2977">
    <title>Draft Update</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2977</link>
    <description>

Ok, I've made some updates, firstly removing specific references to DNS
since this is no longer specifically meant to be for DNS and other
changes to remove references to using the user id field, and instead
using user attributes to have the information in a format much more
suitable for computers, this makes more sense to me than a blob of
string doesn't need to be split up and parsed to extract the information.

http://open-pgp.info/wiki/index.php?title=Standardisation_of_OpenPGP_Keys_for_Server_Purposes

Is there anything I've missed or overlooked at all?

</description>
    <dc:creator>Duane</dc:creator>
    <dc:date>2008-07-27T00:27:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2972">
    <title>OpenPGP Browser Support</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2972</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Duane</dc:creator>
    <dc:date>2008-07-24T05:07:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2963">
    <title>GnuTLS 2.5.2</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2963</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Simon Josefsson</dc:creator>
    <dc:date>2008-07-08T15:44:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2960">
    <title>[PATCH] Little leak fix</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2960</link>
    <description>Hello,

I've found out this via valgrind:

==5806== 7,698 (504 direct, 7,194 indirect) bytes in 9 blocks are 
         definitely lost in loss record 175 of 248
==5806==    at 0x4C220BC: calloc (vg_replace_malloc.c:397)
==5806==    by 0xED2FE11: _asn1_add_node_only (structure.c:54)
==5806==    by 0xED2FFF2: _asn1_copy_structure3 (structure.c:398)
==5806==    by 0xED3038D: asn1_create_element (structure.c:690)
==5806==    by 0x9733F7A: _gnutls_x509_decode_octet_string (common.c:832)
==5806==    by 0x9734243: _gnutls_x509_read_value (common.c:912)
==5806==    by 0x974756E: _decode_pkcs12_auth_safe (pkcs12.c:76)
==5806==    by 0x9748A67: gnutls_pkcs12_get_bag (pkcs12.c:598)

Attached is a patch which fixes it.

HTH,
</description>
    <dc:creator>Colin Leroy</dc:creator>
    <dc:date>2008-07-04T12:07:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2952">
    <title>GnuTLS 2.5.1</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2952</link>
    <description>The GnuTLS 2.5.x branch is NOT what you want for your stable system.  It
is intended for developers and experienced users.

This release should contain no changes other than the result of 'make
indent' compared to v2.5.0.

Here are the compressed sources:
  http://alpha.gnu.org/gnu/gnutls/gnutls-2.5.1.tar.bz2
  ftp://alpha.gnu.org/gnu/gnutls/gnutls-2.5.1.tar.bz2

Improving GnuTLS is costly, but you can help!  We are looking for
organizations that find GnuTLS useful and wish to contribute back.
You can contribute by reporting bugs, improve the software, or donate
money or equipment.

Commercial support contracts for GnuTLS are available, and they help
finance continued maintenance.  Simon Josefsson Datakonsult, a
Stockholm based privately held company, is currently funding GnuTLS
maintenance.  We are always looking for interesting development
projects.  See http://josefsson.org/ for more details.

/Simon

* Version 2.5.1 (released 2008-07-02)

** Indent code.

** API and ABI modifications:
No changes since la</description>
    <dc:creator>Simon Josefsson</dc:creator>
    <dc:date>2008-07-02T15:53:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2951">
    <title>GnuTLS 2.5.0</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2951</link>
    <description>The GnuTLS 2.5.x branch is NOT what you want for your stable system.  It
is intended for developers and experienced users.

This release contains a merge of Nikos' gnutls_with_mpi branch.  It
should now be possible to replace the libgcrypt calls to your own
callbacks.  A lot of low-level code has changed since 2.4.x, so expect
this to be unstable.

I intend to release 2.5.1 shortly after this release, to indent all code
to conform to the GNU Coding Standards.

Here are the compressed sources:
  http://alpha.gnu.org/gnu/gnutls/gnutls-2.5.0.tar.bz2
  ftp://alpha.gnu.org/gnu/gnutls/gnutls-2.5.0.tar.bz2

Improving GnuTLS is costly, but you can help!  We are looking for
organizations that find GnuTLS useful and wish to contribute back.
You can contribute by reporting bugs, improve the software, or donate
money or equipment.

Commercial support contracts for GnuTLS are available, and they help
finance continued maintenance.  Simon Josefsson Datakonsult, a
Stockholm based privately held company, is currently fundin</description>
    <dc:creator>Simon Josefsson</dc:creator>
    <dc:date>2008-07-02T15:52:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2949">
    <title>guile self-tests fail in v.2.5?</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2949</link>
    <description>Hi Ludovic,

On the master trunk there has been some heavy internal changes recently,
but no incompatible API changes as far as I understand, and now the
guile self-tests fails:

make[3]: Entering directory `/home/jas/src/gnutls/guile/tests'
guile: uncaught throw to gnutls-error: (#&lt;gnutls-error-enum The Diffie Hellman prime sent by the server is not acceptable (not long enough).&gt; handshake)
make[3]: *** [check-TESTS] Interrupt

Actually I need to ctrl-c it to cancel it.

Do you have any idea?  How would I debug this, anyway?  I am a bit at a
loss when running into any guile problem.

Thanks,
/Simon
</description>
    <dc:creator>Simon Josefsson</dc:creator>
    <dc:date>2008-06-30T22:23:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2948">
    <title>Details on the gnutls_handshake local crash problem[GNUTLS-SA-2008-2]</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2948</link>
    <description>Below is my analysis of the problem.  The patch is short:

From 0fee3917077e191dea3c9787c95c072979532086 Mon Sep 17 00:00:00 2001
From: Simon Josefsson &lt;simon&lt; at &gt;josefsson.org&gt;
Date: Mon, 30 Jun 2008 22:44:47 +0200
Subject: [PATCH] (_gnutls_handshake_hash_buffers_clear): Make sure deinitialized MAC hashes are initialized.
 Report and tiny patch from Tomas Mraz &lt;tmraz&lt; at &gt;redhat.com&gt;.

---
 lib/gnutls_handshake.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/lib/gnutls_handshake.c b/lib/gnutls_handshake.c
index d798180..0192c9f 100644
--- a/lib/gnutls_handshake.c
+++ b/lib/gnutls_handshake.c
&lt; at &gt;&lt; at &gt; -69,11 +69,12 &lt; at &gt;&lt; at &gt; int _gnutls_server_select_comp_method (gnutls_session_t session,
 
 /* Clears the handshake hash buffers and handles.
  */
-inline static void
+static void
 _gnutls_handshake_hash_buffers_clear (gnutls_session_t session)
 {
   _gnutls_hash_deinit (&amp;session-&gt;internals.handshake_mac_handle_md5, NULL);
   _gnutls_hash_deinit (&amp;session-&gt;internals.handshake_mac_handle_sha, NULL);
+  se</description>
    <dc:creator>Simon Josefsson</dc:creator>
    <dc:date>2008-06-30T21:42:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2947">
    <title>GnuTLS 2.4.1</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2947</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Simon Josefsson</dc:creator>
    <dc:date>2008-06-30T21:36:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2944">
    <title>[PATCH] srptool, fix problem where passwords never match</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2944</link>
    <description>Hi,

this fixes a problem in srptool, where the passwords never match
(--verify check) on some architectures (I think I have observed
this only on i386). It is for 1.6.1, but still applies to 2.4.0.

Matthias

Index: gnutls-1.6.1/src/crypt.c
===================================================================
--- gnutls-1.6.1.orig/src/crypt.c
+++ gnutls-1.6.1/src/crypt.c
&lt; at &gt;&lt; at &gt; -220,6 +220,7 &lt; at &gt;&lt; at &gt; _verify_passwd_int (const char *username
 
   /* encode the verifier into _salt */
   salt_size = sizeof (_salt);
+  memset(_salt, '\0', salt_size);
   if (gnutls_srp_base64_encode (&amp;new_verifier, _salt, &amp;salt_size) &lt; 0)
     {
       fprintf (stderr, "Encoding error\n");
</description>
    <dc:creator>Matthias Koenig</dc:creator>
    <dc:date>2008-06-30T08:21:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2938">
    <title>Memory leak in _gnutls_mpi_dprint_lz (possibly _gnutls_mpi_dprint)</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2938</link>
    <description>I'm chasing a complaint from valgrind that I'm leaking memory.

Here's valgrind's complaint:

==26738== 257 bytes in 1 blocks are definitely lost in loss record 2 of 4
==26738==    at 0x4A0739E: malloc (vg_replace_malloc.c:207)
==26738==    by 0x35068328F6: _gnutls_mpi_dprint_lz (gnutls_mpi.c:146)
==26738==    by 0x350683E47C: _gnutls_dh_set_peer_public (gnutls_state.c:474)
==26738==    by 0x3506843819: _gnutls_proc_dh_common_server_kx (auth_dh_common.c:297)
==26738==    by 0x350683BB4F: proc_dhe_server_kx (auth_dhe.c:199)
==26738==    by 0x350682AF81: _gnutls_recv_server_kx_message (gnutls_kx.c:339)
==26738==    by 0x35068273DF: _gnutls_handshake_client (gnutls_handshake.c:2311)
==26738==    by 0x3506827F77: gnutls_handshake (gnutls_handshake.c:2193)


Here's what I've been able to figure out. I'm running gnutls 2.0.4, but I 
checked 2.4.0, and the affected bits have not changed, the following should 
still be applicable.

_gnutls_mpi_dprint_lz() allocates a buffer:

  if (bytes != 0)
    buf = gnutls_mallo</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2008-06-28T01:01:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2934">
    <title>lib/opencdk/read-packet.c: read_s2k() implementation</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2934</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Daniel Kahn Gillmor</dc:creator>
    <dc:date>2008-06-27T05:50:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2928">
    <title>Memory leak in _gnutls_mpi_dprint_lz (possibly _gnutls_mpi_dprint)</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2928</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2008-06-23T00:25:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2926">
    <title>PEM generated by gnutls_rsa_params_export_pkcs1 and gnutls_dh_params_import_pkcs3</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2926</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Sam Varshavchik</dc:creator>
    <dc:date>2008-06-22T22:28:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2917">
    <title>2.3.15 patches - QA includes to fix compile warnings</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2917</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Daniel Black</dc:creator>
    <dc:date>2008-06-19T09:14:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2912">
    <title>building gnutls 2.3.15 with opencdk installed</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2912</link>
    <description>_______________________________________________
Gnutls-devel mailing list
Gnutls-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gnutls-devel
</description>
    <dc:creator>Roman Bogorodskiy</dc:creator>
    <dc:date>2008-06-19T05:03:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2908">
    <title>2.6.x goals?</title>
    <link>http://comments.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/2908</link>
    <description>Nikos, what is the status of your mpi branch?  Is it ready for me to
review as if we would merge it into master?  Please hold off any merge
until I have reviewed and discussed the changes.

Btw, my goals for 2.5.x is to integrate Nikos' crypto.h stuff, and to
re-indent the code.  As far as I know, there are no other tasks that are
pending, or are there?  Anything major to be included should be made
available on a separate branch for review relatively soon, or it will
have to wait for 2.7.x.

All minor improvements like enhancing self-tests and fixing bugs should
be possible though, but they aren't release goals.  Waiting for
nice-things-to-have like better PKCS#11 integration, GPGME compatibility
etc will delay us, but people should feel free to start working on stuff
like that now anyway, 2.7.x isn't that far away.

Hopefully we can make the 2.5.x release cycle shorter than the last...
It would be nice to have a 2.6.x release candidate ready by August, to
get the crypto.h stuff out.

/Simon
</description>
    <dc:creator>Simon Josefsson</dc:creator>
    <dc:date>2008-06-18T16:07:13</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.encryption.gpg.gnutls.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.encryption.gpg.gnutls.devel</link>
  </textinput>
</rdf:RDF>
