From nmav at gnutls.org  Fri Feb  1 09:19:52 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Fri, 1 Feb 2013 09:19:52 +0100
Subject: [gnutls-help] telling gnutls-cli to avoid sending SNI
In-Reply-To: <87wquv6961.fsf@alice.fifthhorseman.net>
References: <87wquv6961.fsf@alice.fifthhorseman.net>
Message-ID: <CAJU7za+kZ9i6hDShwnZ6QCoq_cr8_nFmUQZpccN492i1-KapjA@mail.gmail.com>

On Tue, Jan 29, 2013 at 9:12 PM, Daniel Kahn Gillmor
<dkg at fifthhorseman.net> wrote:
> any ideas about how i should proceed with this?

Hello Daniel,
 Just ignore the generated files in the patch. They are there for
convenience. Don't need to send patches on them.

regards,
Nikos


From dkg at fifthhorseman.net  Fri Feb  1 09:44:27 2013
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Fri, 01 Feb 2013 03:44:27 -0500
Subject: [gnutls-help] telling gnutls-cli to avoid sending SNI
In-Reply-To: <CAJU7za+kZ9i6hDShwnZ6QCoq_cr8_nFmUQZpccN492i1-KapjA@mail.gmail.com>
References: <87wquv6961.fsf@alice.fifthhorseman.net>
	<CAJU7za+kZ9i6hDShwnZ6QCoq_cr8_nFmUQZpccN492i1-KapjA@mail.gmail.com>
Message-ID: <510B806B.4020500@fifthhorseman.net>

On 02/01/2013 03:19 AM, Nikos Mavrogiannopoulos wrote:
>  Just ignore the generated files in the patch. They are there for
> convenience. Don't need to send patches on them.

Hm, ok, then i think that means just the cli-disable-sni.patch i sent
originally (though i can't seem to test it properly because of the
autogen conflicts i'm seeing with my current build environment).

Do you need anything else to consider that patch for inclusion in the trunk?

Or are there some guidelines i should follow for fully-re-autogen'ing
the tree to try to avoid the conflicts and test it locally?

Thanks,

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1027 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20130201/8459874b/attachment.pgp>

From nmav at gnutls.org  Mon Feb  4 10:28:11 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Mon, 04 Feb 2013 10:28:11 +0100
Subject: [gnutls-help] gnutls 3.0.28
Message-ID: <510F7F2B.5060208@gnutls.org>

Hello,
 I've just released gnutls 3.0.28. This is a bug-fix release on the
previous stable branch.

* Version 3.0.28 (2012-02-04)

** libgnutls: Fixes in server side of DTLS-0.9.

** libgnutls: Corrected gnutls_cipher_decrypt2() when used with AEAD
ciphers (i.e., AES-GCM).

** libgnutls: Fixes in record padding parsing to prevent a timing
attack. Issue reported by Kenny Patterson and Nadhem Alfardan.

** libgnutls: DN variable 'T' was expanded to 'title'.

** API and ABI modifications:
No changes since last version.


Getting the Software
====================

GnuTLS may be downloaded directly from
<ftp://ftp.gnutls.org/gcrypt/gnutls/>.  A list of GnuTLS mirrors can be
found at <http://www.gnutls.org/download.html>.

Here are the XZ and LZIP compressed sources:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.0/gnutls-3.0.28.tar.xz
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.0/gnutls-3.0.28.tar.lz

Here are OpenPGP detached signatures signed using key 0x96865171:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.0/gnutls-3.0.28.tar.xz.sig
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.0/gnutls-3.0.28.tar.lz.sig

Note that it has been signed with my openpgp key:
pub   3104R/96865171 2008-05-04 [expires: 2028-04-29]
uid                  Nikos Mavrogiannopoulos <nmav <at> gnutls.org>
uid                  Nikos Mavrogiannopoulos <n.mavrogiannopoulos <at>
gmail.com>
sub   2048R/9013B842 2008-05-04 [expires: 2018-05-02]
sub   2048R/1404A91D 2008-05-04 [expires: 2018-05-02]

regards,
Nikos


From nmav at gnutls.org  Mon Feb  4 10:29:34 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Mon, 04 Feb 2013 10:29:34 +0100
Subject: [gnutls-help] gnutls 2.12.23
Message-ID: <510F7F7E.4060003@gnutls.org>

Hello,
 I've just released gnutls 2.12.22. This is a bug-fix release on the
previous stable branch.

Version 2.12.23 (released 2012-02-04)

** libgnutls: Eliminated memory leak in PCKS #11 initialization.
Report and fix by Sam Varshavchik.

** libgnutls: Fixes in record padding parsing to prevent a timing attack.
Issue reported by Kenny Patterson and Nadhem Alfardan.

** libgnutls: DN variable 'T' was expanded to 'title'.

** API and ABI modifications:
No changes since last version.


Getting the Software
====================

GnuTLS may be downloaded directly from
<ftp://ftp.gnutls.org/gcrypt/gnutls/>.  A list of GnuTLS mirrors can be
found at <http://www.gnutls.org/download.html>.

Here are the compressed sources:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v2.12/gnutls-2.12.23.tar.bz2

Here are OpenPGP detached signatures signed using key 0x96865171:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.0/gnutls-2.12.23.tar.bz2.sig

Note that it has been signed with my openpgp key:
pub   3104R/96865171 2008-05-04 [expires: 2028-04-29]
uid                  Nikos Mavrogiannopoulos <nmav <at> gnutls.org>
uid                  Nikos Mavrogiannopoulos <n.mavrogiannopoulos <at>
gmail.com>
sub   2048R/9013B842 2008-05-04 [expires: 2018-05-02]
sub   2048R/1404A91D 2008-05-04 [expires: 2018-05-02]

regards,
Nikos


From nmav at gnutls.org  Mon Feb  4 11:25:43 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Mon, 04 Feb 2013 11:25:43 +0100
Subject: [gnutls-help] gnutls 3.1.7
Message-ID: <510F8CA7.6090203@gnutls.org>

Hello,
 I've just released gnutls 3.1.7. This is a new release on the current
stable branch. Note that this release includes a new gnutls-xssl library
which provides a very simple API to use. The new API is demonstrated in
[0]. We welcome comments on the new API.

[0]. http://www.gnutls.org/manual/html_node/XSSL-examples.html#XSSL-examples


* Version 3.1.7 (released 2012-02-04)

** certtool: Added option "dn" which allows to directly set the DN
in a template from an RFC4514 string.

** danetool: Added options: --dlv and --insecure. Suggested by Paul Wouters.

** libgnutls-xssl: Added a new library to simplify GnuTLS usage.

** libgnutls-dane: Added function to specify a DLV file.

** libgnutls: Heartbeat code was made optional.

** libgnutls: Fixes in server side of DTLS-0.9.

** libgnutls: DN variable 'T' was expanded to 'title'.

** libgnutls: Fixes in record padding parsing to prevent a timing
attack. Issue reported by Kenny Paterson and Nadhem Alfardan.

** libgnutls: Added functions to directly set the DN in a certificate
or request from an RFC4514 string.

** libgnutls: Optimizations in the random generator. The re-seeding of
it is now explicitly done on every session deinit.

** libgnutls: Simplified the DTLS sliding window implementation.

** libgnutls: The minimum DH bits accepted by a client are now set
by the specified priority string. The current values correspond to the
previous defaults (727 bits), except for the SECURE128 and SECURE192
strings which increase the minimum to 1248 and 1776 respectively.

** libgnutls: Added the gnutls_record_cork() and uncork API to enable
buffering in sending application data.

** libgnutls: Removed default random padding, and added a length-hiding
interface instead.  Both the server and the client must support this
extension. Whether length-hiding can be used on a given session can be
checked using gnutls_record_can_use_length_hiding(). Contributed by
Alfredo Pironti.

** libgnutls: Added the experimental %NEW_PADDING priority string. It
enables a new padding mechanism in TLS allowing arbitrary padding in TLS
records in all ciphersuites, which makes length-hiding more efficient
and solves the issues with timing attacks on CBC ciphersuites.

** libgnutls: Corrected gnutls_cipher_decrypt2() when used with AEAD
ciphers (i.e., AES-GCM). Reported by William McGovern.

** API and ABI modifications:
gnutls_db_check_entry_time: Added
gnutls_record_set_timeout: Added
gnutls_record_get_random_padding_status: Added
gnutls_x509_crt_set_dn: Added
gnutls_x509_crt_set_issuer_dn: Added
gnutls_x509_crq_set_dn: Added
gnutls_record_cork: Added
gnutls_record_uncork: Added
gnutls_range_split: Added
gnutls_record_send_range: Added
gnutls_record_set_max_empty_records: Added
gnutls_record_can_use_length_hiding: Added
gnutls_rnd_refresh: Added
xssl_deinit: Added
xssl_flush: Added
xssl_read: Added
xssl_getdelim: Added
xssl_write: Added
xssl_printf: Added
xssl_sinit: Added
xssl_client_init: Added
xssl_server_init: Added
xssl_get_session: Added
xssl_get_verify_status: Added
xssl_cred_init: Added
xssl_cred_deinit: Added
dane_state_set_dlv_file: Added
GNUTLS_SEC_PARAM_EXPORT: Added
GNUTLS_SEC_PARAM_VERY_WEAK: Added



Getting the Software
====================

GnuTLS may be downloaded directly from
<ftp://ftp.gnutls.org/gcrypt/gnutls/>.  A list of GnuTLS mirrors can be
found at <http://www.gnutls.org/download.html>.

Here are the XZ and LZIP compressed sources:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.7.tar.xz
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.7.tar.lz

Here are OpenPGP detached signatures signed using key 0x96865171:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.7.tar.xz.sig
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.7.tar.lz.sig

Note that it has been signed with my openpgp key:
pub   3104R/96865171 2008-05-04 [expires: 2028-04-29]
uid                  Nikos Mavrogiannopoulos <nmav <at> gnutls.org>
uid                  Nikos Mavrogiannopoulos <n.mavrogiannopoulos <at>
gmail.com>
sub   2048R/9013B842 2008-05-04 [expires: 2018-05-02]
sub   2048R/1404A91D 2008-05-04 [expires: 2018-05-02]

regards,
Nikos


From nmav at gnutls.org  Mon Feb  4 18:21:04 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Mon, 04 Feb 2013 18:21:04 +0100
Subject: [gnutls-help] advisory GNUTLS-SA-2013-1
Message-ID: <510FEE00.8090502@gnutls.org>

Hello,
 I've put online a security advisory on the "lucky 13" CBC ciphersuite
attack in [0]. The advisory can be found at:
http://www.gnutls.org/security.html#GNUTLS-SA-2013-1

[0]. http://www.isg.rhul.ac.uk/tls/

regards,
Nikos


From yanfiz at gmail.com  Tue Feb  5 20:43:42 2013
From: yanfiz at gmail.com (Yan Fiz)
Date: Tue, 5 Feb 2013 21:43:42 +0200
Subject: [gnutls-help] Generating a certificate with an encrypted private key
Message-ID: <CAL=Q3ePqwpNHXdKTbUJ+um_moRWx__v7Fs9PPfGaE968QVpEFQ@mail.gmail.com>

Hello,

I tried to generate a self signed certificate with an encrypted private
key. GnuTLS 3.0.22 is OK, but GnuTLS 3.1.7 gives error with the same
commands.

D:\gnutls-3.0.22-w32\bin>certtool.exe --generate-privkey --pkcs8
--pkcs-cipher aes-256 --rsa --bits 2048 --outfile test.p8
** Note: Please use the --sec-param instead of --bits
Generating a 2048 bit RSA private key...
Enter password:
Confirm password:

D:\gnutls-3.0.22-w32\bin>certtool.exe --generate-self-signed --pkcs8 --hash
sha512 --load-privkey test.p8 --outfile test.crt
Generating a self signed certificate...
Enter password:
Please enter the details of the certificate's distinguished name. Just
press enter to ignore a field.
Country name (2 chars):
.
.
.

D:\gnutls-3.1.7-w32\bin>certtool.exe --generate-privkey --pkcs8
--pkcs-cipher aes-256 --rsa --bits 2048 --outfile test.p8
** Note: Please use the --sec-param instead of --bits
Generating a 2048 bit RSA private key...
Enter password:

D:\gnutls-3.1.7-w32\bin>certtool.exe --generate-self-signed --pkcs8 --hash
sha512 --load-privkey test.p8 --outfile test.crt
Generating a self signed certificate...
certtool.exe: import error: could not find a valid PEM header; check if
your key is PKCS #12 encoded

D:\gnutls-3.1.7-w32\bin>certtool.exe --generate-self-signed --pkcs8 --hash
sha512 --load-privkey test.p8 --outfile test.crt --debug 9999
Setting log level to 9999
|<2>| Intel AES accelerator was detected
|<2>| ASSERT: pkcs11.c:456
Generating a self signed certificate...
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN RSA PRIVATE KEY'
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN DSA PRIVATE KEY'
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN EC PRIVATE KEY'
|<2>| ASSERT: privkey.c:484
|<2>| Falling back to PKCS #8 key decoding
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN PRIVATE KEY'
|<2>| ASSERT: privkey_pkcs8.c:1199
|<2>| ASSERT: privkey_pkcs8.c:1351
|<2>| ASSERT: privkey.c:638
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN PRIVATE KEY'
|<9>| keyDerivationFunc.algorithm: 1.2.840.113549.1.5.12
|<9>| salt.specified.size: 14
|<9>| iterationCount: 263
|<2>| ASSERT: mpi.c:246
|<9>| keyLength: 0
|<9>| encryptionScheme.algorithm: 2.16.840.1.101.3.4.1.42
|<9>| IV.size: 16
|<2>| ASSERT: privkey_pkcs8.c:1199
|<2>| ASSERT: privkey_pkcs8.c:998
|<2>| ASSERT: privkey_pkcs8.c:1351
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN PKCS12'
|<2>| ASSERT: pkcs12.c:216
|<2>| ASSERT: privkey.c:577
|<2>| ASSERT: privkey_openssl.c:158
|<2>| ASSERT: privkey.c:655
|<2>| ASSERT: gnutls_privkey.c:932
certtool.exe: import error: could not find a valid PEM header; check if
your key is PKCS #12 encoded
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20130205/0df38adb/attachment-0001.htm>

From mk at cognitivedissonance.ca  Wed Feb  6 17:58:10 2013
From: mk at cognitivedissonance.ca (MK)
Date: Wed, 6 Feb 2013 11:58:10 -0500
Subject: [gnutls-help] nettle and hogweed
Message-ID: <20130206115810.5592f339cee30a8c7fe03c6d@cognitivedissonance.ca>

You need to fix configure so that makes a check for libhogweed
*explicit* instead of bailing out by saying "could not find nettle"!

[I just posted a whiny related note to the gnutls-devel list address
by accident, to which I don't subscribe.  Hopefully that bounced --
sorry]

Anyway, I had googled and the only thing I found was another note from
a year or so ago to which Nikos said, "Well, it works for me", lol.

http://lists.gnu.org/archive/html/help-gnutls/2011-12/msg00021.html

Perhaps, not the only person who has gotten snagged with this and may
have never found the solution:

http://stackoverflow.com/questions/7702656/error-when-cross-compiling-gnutls

Anyway, I looked in the config.log, saw the -lhogweed bit, googled
about that, and found more mail from Nikos last month explaining the
libnettle - gmp - hogweed issue.

Maybe putting a note on the web page would be nice too.  I just wasted
a half hour on this. :(

-- 
"Enthusiasm is not the enemy of the intellect." (said of Irving Howe)
"The angel of history[...]is turned toward the past." (Walter Benjamin)



From daniel at pocock.com.au  Wed Feb  6 22:46:22 2013
From: daniel at pocock.com.au (Daniel Pocock)
Date: Wed, 06 Feb 2013 22:46:22 +0100
Subject: [gnutls-help] gnutls used in dynalogin now
Message-ID: <5112CF2E.5010301@pocock.com.au>



Hi,

I needed to implement TLS for dynalogin and I've chosen gnutls.

So far, I've just borrowed the public domain sample X509 client/server
code from the gnutls packages on my dev machines.  However, as I haven't
integrated with gnutls before, if anybody has time to review my code (it
is all open source GPL) I'd really appreciate any comments about whether
this is sufficient or secure

One problem I found is the differences between the samples available on
the web, the samples in a Debian 6 system and the samples in a Debian
wheezy system.  I ended up trying different permutations and finally
mangling them to work for the Debian 7 (wheezy) system rather than the
latest version of gnutls

This is the server side:

  https://github.com/dynalogin/dynalogin/tree/master/dynalogind

and the client side:

  https://github.com/dynalogin/dynalogin/tree/master/libdynaloginclient

Regards,

Daniel


From nmav at gnutls.org  Thu Feb  7 14:03:16 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Thu, 7 Feb 2013 14:03:16 +0100
Subject: [gnutls-help] Generating a certificate with an encrypted
	private key
In-Reply-To: <CAL=Q3ePqwpNHXdKTbUJ+um_moRWx__v7Fs9PPfGaE968QVpEFQ@mail.gmail.com>
References: <CAL=Q3ePqwpNHXdKTbUJ+um_moRWx__v7Fs9PPfGaE968QVpEFQ@mail.gmail.com>
Message-ID: <CAJU7zaLyUjJ6u_H509UEeX6B0fiLAZG2MZHNRLaHm0cbtVd15g@mail.gmail.com>

On Tue, Feb 5, 2013 at 8:43 PM, Yan Fiz <yanfiz at gmail.com> wrote:
> Hello,
>
> I tried to generate a self signed certificate with an encrypted private key.
> GnuTLS 3.0.22 is OK, but GnuTLS 3.1.7 gives error with the same commands.

Thank you for the bug report. Could you check if the attached patch
solves the issue?

regards,
Nikos
-------------- next part --------------
diff --git a/lib/x509/privkey.c b/lib/x509/privkey.c
index 7b31821..586dc09 100644
--- a/lib/x509/privkey.c
+++ b/lib/x509/privkey.c
@@ -642,10 +642,10 @@ gnutls_x509_privkey_import2 (gnutls_x509_privkey_t key,
   if ((password != NULL || (flags & GNUTLS_PKCS_NULL_PASSWORD)) || ret < 0)
     {
       ret = gnutls_x509_privkey_import_pkcs8(key, data, format, password, flags);
-      if (ret < 0)
+      if (ret < 0 && ret != GNUTLS_E_DECRYPTION_FAILED)
         {
           ret = import_pkcs12_privkey(key, data, format, password, flags);
-          if (ret < 0 && format == GNUTLS_X509_FMT_PEM)
+          if (ret < 0 && ret != GNUTLS_E_DECRYPTION_FAILED && format == GNUTLS_X509_FMT_PEM)
             {
               int err;
               err = gnutls_x509_privkey_import_openssl(key, data, password);

From yanfiz at gmail.com  Fri Feb  8 00:39:37 2013
From: yanfiz at gmail.com (Yan Fiz)
Date: Fri, 8 Feb 2013 01:39:37 +0200
Subject: [gnutls-help] Generating a certificate with an encrypted
	private key
In-Reply-To: <CAJU7zaLyUjJ6u_H509UEeX6B0fiLAZG2MZHNRLaHm0cbtVd15g@mail.gmail.com>
References: <CAL=Q3ePqwpNHXdKTbUJ+um_moRWx__v7Fs9PPfGaE968QVpEFQ@mail.gmail.com>
	<CAJU7zaLyUjJ6u_H509UEeX6B0fiLAZG2MZHNRLaHm0cbtVd15g@mail.gmail.com>
Message-ID: <CAL=Q3ePXKFrekPh8M7CX9yR1ONwKASFtCBA9GbjSZA1o4FiTWA@mail.gmail.com>

On Thu, Feb 7, 2013 at 3:03 PM, Nikos Mavrogiannopoulos <nmav at gnutls.org>wrote:

> On Tue, Feb 5, 2013 at 8:43 PM, Yan Fiz <yanfiz at gmail.com> wrote:
> > Hello,
> >
> > I tried to generate a self signed certificate with an encrypted private
> key.
> > GnuTLS 3.0.22 is OK, but GnuTLS 3.1.7 gives error with the same commands.
>
> Thank you for the bug report. Could you check if the attached patch
> solves the issue?
>
> regards,
> Nikos
>

Hello,

Thanks for your reply. I noticed this bug, while I was trying to generate
some certificates for vpn. I would want to check that attached patch, but
I'm not good at patching and recompiling source codes :( I'm not a
developer, just a user. Forgive me. If you release a beta version for
Windows, I will check if that patch solves the issue.

Kind regards,
Yan Fiz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20130208/152a4649/attachment.htm>

From nmav at gnutls.org  Fri Feb  8 09:05:54 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Fri, 8 Feb 2013 09:05:54 +0100
Subject: [gnutls-help] Generating a certificate with an encrypted
	private key
In-Reply-To: <CAL=Q3ePXKFrekPh8M7CX9yR1ONwKASFtCBA9GbjSZA1o4FiTWA@mail.gmail.com>
References: <CAL=Q3ePqwpNHXdKTbUJ+um_moRWx__v7Fs9PPfGaE968QVpEFQ@mail.gmail.com>
	<CAJU7zaLyUjJ6u_H509UEeX6B0fiLAZG2MZHNRLaHm0cbtVd15g@mail.gmail.com>
	<CAL=Q3ePXKFrekPh8M7CX9yR1ONwKASFtCBA9GbjSZA1o4FiTWA@mail.gmail.com>
Message-ID: <CAJU7zaJgYDgN-XokAF8cXMHaXTPG-tdF9CuNFV3X4Kr8B8d-JQ@mail.gmail.com>

>> Thank you for the bug report. Could you check if the attached patch
>> solves the issue?
> Thanks for your reply. I noticed this bug, while I was trying to generate
> some certificates for vpn. I would want to check that attached patch, but
> I'm not good at patching and recompiling source codes :( I'm not a
> developer, just a user. Forgive me. If you release a beta version for
> Windows, I will check if that patch solves the issue.

There was an issue in the patch which I've corrected it in the
repository. Until the next release you may work around it by
generating an unencrypted key and encrypting it after the certificate
is also generated.

regards,
Nikos


From nmav at gnutls.org  Sun Feb 10 12:57:43 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Sun, 10 Feb 2013 12:57:43 +0100
Subject: [gnutls-help] gnutls 3.1.8
Message-ID: <51178B37.9040009@gnutls.org>

Hello,
 I've just released gnutls 3.1.8. This is bug fix release on the current
stable branch. GnuTLS 3.1.7 inadvertently increased the security level
of the priority string NORMAL. This release restores it to the levels of
GnuTLS 3.1.6.


* Version 3.1.8 (released 2013-02-10)

** libgnutls: Fixed issue in gnutls_x509_privkey_import2() which didn't
return GNUTLS_E_DECRYPTION_FAILED in all cases, and affect certtool
operation with encrypted keys. Reported by Yan Fiz.

** libgnutls: The minimum DH bits accepted by priorities NORMAL and
PERFORMANCE was set to previous defaults 727 bits. Reported by Diego
Elio Petteno.

** libgnutls: Corrected issue which prevented
gnutls_pubkey_verify_hash() to operate with long keys. Reported by Erik
A Jensen.

** API and ABI modifications:
No changes since last version.


Getting the Software
====================

GnuTLS may be downloaded directly from
<ftp://ftp.gnutls.org/gcrypt/gnutls/>.  A list of GnuTLS mirrors can be
found at <http://www.gnutls.org/download.html>.

Here are the XZ and LZIP compressed sources:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.8.tar.xz
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.8.tar.lz

Here are OpenPGP detached signatures signed using key 0x96865171:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.8.tar.xz.sig
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.8.tar.lz.sig

Note that it has been signed with my openpgp key:
pub   3104R/96865171 2008-05-04 [expires: 2028-04-29]
uid                  Nikos Mavrogiannopoulos <nmav <at> gnutls.org>
uid                  Nikos Mavrogiannopoulos <n.mavrogiannopoulos <at>
gmail.com>
sub   2048R/9013B842 2008-05-04 [expires: 2018-05-02]
sub   2048R/1404A91D 2008-05-04 [expires: 2018-05-02]

regards,
Nikos


From yanfiz at gmail.com  Sun Feb 10 20:18:12 2013
From: yanfiz at gmail.com (Yan Fiz)
Date: Sun, 10 Feb 2013 21:18:12 +0200
Subject: [gnutls-help] Generating a certificate with an encrypted
	private key
In-Reply-To: <CAJU7zaJgYDgN-XokAF8cXMHaXTPG-tdF9CuNFV3X4Kr8B8d-JQ@mail.gmail.com>
References: <CAL=Q3ePqwpNHXdKTbUJ+um_moRWx__v7Fs9PPfGaE968QVpEFQ@mail.gmail.com>
	<CAJU7zaLyUjJ6u_H509UEeX6B0fiLAZG2MZHNRLaHm0cbtVd15g@mail.gmail.com>
	<CAL=Q3ePXKFrekPh8M7CX9yR1ONwKASFtCBA9GbjSZA1o4FiTWA@mail.gmail.com>
	<CAJU7zaJgYDgN-XokAF8cXMHaXTPG-tdF9CuNFV3X4Kr8B8d-JQ@mail.gmail.com>
Message-ID: <CAL=Q3eP=ATE_4SH_L91EC=dSf9du=Pu2xmuDVLktxA_xCH7Z4g@mail.gmail.com>

Hello,

GnuTLS 3.1.8 can generate a certificate with an encrypted private key
(thank you for fixing it), but cannot generate a PKCS #12 structure with
that encrypted private key and that certificate, while GnuTLS 3.0.22 can.

Kind regards,
Yan Fiz.

D:\gnutls-3.0.22-w32\bin>certtool.exe --generate-privkey --pkcs8
--pkcs-cipher aes-256 --rsa --sec-param normal --outfile test.p8
Generating a 2432 bit RSA private key...
Enter password:
Confirm password:

D:\gnutls-3.0.22-w32\bin>certtool.exe --generate-self-signed --pkcs8 --hash
sha512 --load-privkey test.p8 --outfile test.crt
Generating a self signed certificate...
Enter password:
Please enter the details of the certificate's distinguished name. Just
press enter to ignore a field.
Country name (2 chars):
.
.
.

D:\gnutls-3.0.22-w32\bin>certtool.exe --to-p12 --pkcs-cipher arcfour
--pkcs8 --outder --load-privkey test.p8 --load-certificate test.crt
--outfile test.p12
Generating a PKCS #12 structure...
Enter password:
Loading certificate list...
Loaded 1 certificates.
Enter a name for the key: Test
Enter password:

D:\gnutls-3.1.8-w32\bin>certtool.exe --generate-privkey --pkcs8
--pkcs-cipher aes-256 --rsa --sec-param normal --outfile test.p8
Generating a 2432 bit RSA private key...
Enter password:

D:\gnutls-3.1.8-w32\bin>certtool.exe --generate-self-signed --pkcs8 --hash
sha512 --load-privkey test.p8 --outfile test.crt
Generating a self signed certificate...
Enter password:
Please enter the details of the certificate's distinguished name. Just
press enter to ignore a field.
Common name:
.
.
.

D:\gnutls-3.1.8-w32\bin>certtool.exe --to-p12 --pkcs-cipher arcfour --pkcs8
--outder --load-privkey test.p8 --load-certificate test.crt --outfile
test.p12
Generating a PKCS #12 structure...
Loading private key list...
certtool.exe: privkey_import: Decryption has failed.

D:\gnutls-3.1.8-w32\bin>certtool.exe --to-p12 --pkcs-cipher arcfour --pkcs8
--outder --load-privkey test.p8 --load-certificate test.crt --outfile
test.p12 --debug 9999
Setting log level to 9999
|<2>| Intel AES accelerator was detected
|<2>| ASSERT: pkcs11.c:456
Generating a PKCS #12 structure...
Loading private key list...
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN RSA PRIVATE KEY'
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN DSA PRIVATE KEY'
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN EC PRIVATE KEY'
|<2>| ASSERT: privkey.c:484
|<2>| Falling back to PKCS #8 key decoding
|<2>| ASSERT: x509_b64.c:306
|<2>| Could not find '-----BEGIN PRIVATE KEY'
|<2>| ASSERT: privkey_pkcs8.c:1199
|<2>| ASSERT: privkey_pkcs8.c:1351
certtool.exe: privkey_import: Decryption has failed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20130210/9484497c/attachment-0001.htm>

From frederic.dreier at gmail.com  Mon Feb 11 17:48:36 2013
From: frederic.dreier at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Dreier?=)
Date: Mon, 11 Feb 2013 17:48:36 +0100
Subject: [gnutls-help] gnutls-cli and apache
Message-ID: <CAA5b1Et470t2Ay0U+EJMbPMS18Q3iqhi0HYc+Y1fDXMM=tC75Q@mail.gmail.com>

Hi,

I try since some hours deploy a webdav server using apache under ubuntu
12.4 using client certificates.

I already setup apache+webdav and I can access it through firefox using the
client certificate.

Now I want to use davfs2 which use gnutls but it exits with an gnutls error
(handshake failed, no details)

I tried with gnutls-cli and I also get an error (with more details), but I
am not able to understand it (or what is incorrect).

gnutls-cli -d 9 --x509cafile ca.crt --x509keyfile client.key --x509certfile
client.crt -p 443 myserver
Processed 1 CA certificate(s).
Processed 1 client certificates...
Processed 1 client X.509 certificates...
Resolving 'myserver'...
Connecting to '192.168.1.10:443'...
|<4>| REC[0x1495a80]: Allocating epoch #0
|<2>| ASSERT: gnutls_constate.c:695
|<4>| REC[0x1495a80]: Allocating epoch #1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_AES_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_AES_128_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_CAMELLIA_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_AES_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_AES_256_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_CAMELLIA_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_3DES_EDE_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_AES_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_AES_128_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_CAMELLIA_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_AES_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_AES_256_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_CAMELLIA_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_3DES_EDE_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_ARCFOUR_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_AES_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_AES_128_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_CAMELLIA_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_AES_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_AES_256_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_CAMELLIA_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_3DES_EDE_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_ARCFOUR_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_ARCFOUR_MD5
|<2>| EXT[0x1495a80]: Sending extension SERVER NAME (19 bytes)
|<2>| EXT[0x1495a80]: Sending extension SAFE RENEGOTIATION (1 bytes)
|<2>| EXT[0x1495a80]: Sending extension SESSION TICKET (0 bytes)
|<2>| EXT[SIGA]: sent signature algo (4.2) DSA-SHA256
|<2>| EXT[SIGA]: sent signature algo (4.1) RSA-SHA256
|<2>| EXT[SIGA]: sent signature algo (2.1) RSA-SHA1
|<2>| EXT[SIGA]: sent signature algo (2.2) DSA-SHA1
|<2>| EXT[0x1495a80]: Sending extension SIGNATURE ALGORITHMS (10 bytes)
|<3>| HSK[0x1495a80]: CLIENT HELLO was sent [139 bytes]
|<4>| REC[0x1495a80]: Sending Packet[0] Handshake(22) with length: 139
|<4>| REC[0x1495a80]: Sent Packet[1] Handshake(22) with length: 144
|<4>| REC[0x1495a80]: Expected Packet[0] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[0] Alert(21) with length: 2
|<4>| REC[0x1495a80]: Decrypted Packet[0] Alert(21) with length: 2
|<4>| REC[0x1495a80]: Alert[1|112] - The server name sent was not
recognized - was received
|<2>| ASSERT: gnutls_record.c:726
|<2>| ASSERT: gnutls_record.c:1122
*** Non fatal error: A TLS warning alert has been received.
*** Received alert [112]: The server name sent was not recognized
|<4>| REC[0x1495a80]: Expected Packet[1] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[1] Handshake(22) with length: 57
|<4>| REC[0x1495a80]: Decrypted Packet[1] Handshake(22) with length: 57
|<3>| HSK[0x1495a80]: SERVER HELLO was received [57 bytes]
|<3>| HSK[0x1495a80]: Server's version: 3.3
|<3>| HSK[0x1495a80]: SessionID length: 0
|<3>| HSK[0x1495a80]: SessionID: 00
|<3>| HSK[0x1495a80]: Selected cipher suite: DHE_RSA_AES_128_CBC_SHA1
|<2>| EXT[0x1495a80]: Parsing extension 'SERVER NAME/0' (0 bytes)
|<2>| EXT[0x1495a80]: Parsing extension 'SAFE RENEGOTIATION/65281' (1 bytes)
|<2>| EXT[0x1495a80]: Parsing extension 'SESSION TICKET/35' (0 bytes)
|<3>| HSK[0x1495a80]: Safe renegotiation succeeded
|<4>| REC[0x1495a80]: Expected Packet[2] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[2] Handshake(22) with length: 2510
|<4>| REC[0x1495a80]: Decrypted Packet[2] Handshake(22) with length: 2510
|<3>| HSK[0x1495a80]: CERTIFICATE was received [2510 bytes]
|<2>| ASSERT: ext_signature.c:388
|<2>| ASSERT: ext_signature.c:388
|<2>| ASSERT: mpi.c:609
|<2>| ASSERT: dn.c:1209
|<4>| REC[0x1495a80]: Expected Packet[3] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[3] Handshake(22) with length: 527
|<4>| REC[0x1495a80]: Decrypted Packet[3] Handshake(22) with length: 527
|<3>| HSK[0x1495a80]: SERVER KEY EXCHANGE was received [527 bytes]
|<3>| HSK[0x1495a80]: verify handshake data: using RSA-SHA256
|<2>| ASSERT: ext_signature.c:388
|<4>| REC[0x1495a80]: Expected Packet[4] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[4] Handshake(22) with length: 97
|<4>| REC[0x1495a80]: Decrypted Packet[4] Handshake(22) with length: 97
|<3>| HSK[0x1495a80]: CERTIFICATE REQUEST was received [93 bytes]
|<2>| EXT[SIGA]: rcvd signature algo (6.1) RSA-SHA512
|<2>| EXT[SIGA]: rcvd signature algo (6.2) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (6.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (5.1) RSA-SHA384
|<2>| EXT[SIGA]: rcvd signature algo (5.2) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (5.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (4.1) RSA-SHA256
|<2>| EXT[SIGA]: rcvd signature algo (4.2) DSA-SHA256
|<2>| EXT[SIGA]: rcvd signature algo (4.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (3.1) RSA-SHA224
|<2>| EXT[SIGA]: rcvd signature algo (3.2) DSA-SHA224
|<2>| EXT[SIGA]: rcvd signature algo (3.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (2.1) RSA-SHA1
|<2>| EXT[SIGA]: rcvd signature algo (2.2) DSA-SHA1
|<2>| EXT[SIGA]: rcvd signature algo (2.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (1.1) RSA-MD5
|<3>| HSK[0x1495a80]: SERVER HELLO DONE was received [4 bytes]
|<3>| HSK[0x1495a80]: CERTIFICATE was sent [1137 bytes]
|<3>| HSK[0x1495a80]: CLIENT KEY EXCHANGE was sent [134 bytes]
|<2>| sign handshake cert vrfy: picked RSA-SHA512 with SHA512
|<2>| ASSERT: gnutls_sig.c:630
|<2>| ASSERT: auth_cert.c:1562
|<2>| ASSERT: gnutls_kx.c:336
|<2>| ASSERT: gnutls_handshake.c:2833
*** Fatal error: GnuTLS internal error.
|<4>| REC: Sending Alert[2|80] - Internal error
|<4>| REC[0x1495a80]: Sending Packet[1] Alert(21) with length: 2
|<4>| REC[0x1495a80]: Sent Packet[2] Alert(21) with length: 7
*** Handshake has failed
GnuTLS error: GnuTLS internal error.
|<4>| REC[0x1495a80]: Epoch #0 freed
|<4>| REC[0x1495a80]: Epoch #1 freed


Using "openssl client -connect ..." I am able to connect apache with the
client certificate and execute a GET request.

I only found one post refering to unimplemented SHA512 in gnutls. Is that
the reason?

I tried to switch to gnutls_mod in apache. It works BUT I have other issues
since a lot of functionalities are not implemented there (DN filtering,
fakeauth, etc)

Best regards,

Frederic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20130211/ce9cc1d9/attachment.htm>

From nmav at gnutls.org  Tue Feb 12 09:21:46 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Tue, 12 Feb 2013 09:21:46 +0100
Subject: [gnutls-help] gnutls-cli and apache
In-Reply-To: <CAA5b1Et470t2Ay0U+EJMbPMS18Q3iqhi0HYc+Y1fDXMM=tC75Q@mail.gmail.com>
References: <CAA5b1Et470t2Ay0U+EJMbPMS18Q3iqhi0HYc+Y1fDXMM=tC75Q@mail.gmail.com>
Message-ID: <5119FB9A.5000800@gnutls.org>

On 02/11/2013 05:48 PM, Fr?d?ric Dreier wrote:

> Hi,
> 
> I try since some hours deploy a webdav server using apache under ubuntu
> 12.4 using client certificates.
[...]

> Now I want to use davfs2 which use gnutls but it exits with an gnutls
error (handshake failed, no details)

> 
> I tried with gnutls-cli and I also get an error (with more details), but I
> am not able to understand it (or what is incorrect).
[...]
> I only found one post refering to unimplemented SHA512 in gnutls. Is that
> the reason?


Hello,
 Which version of gnutls is that? Note that many distributions have many
years old gnutls. If this is the case, try using a recent version of
gnutls from www.gnutls.org.

regards,
Nikos


From frederic.dreier at gmail.com  Tue Feb 12 10:10:15 2013
From: frederic.dreier at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Dreier?=)
Date: Tue, 12 Feb 2013 10:10:15 +0100
Subject: [gnutls-help] gnutls-cli and apache
In-Reply-To: <5119FB9A.5000800@gnutls.org>
References: <CAA5b1Et470t2Ay0U+EJMbPMS18Q3iqhi0HYc+Y1fDXMM=tC75Q@mail.gmail.com>
	<5119FB9A.5000800@gnutls.org>
Message-ID: <CAA5b1EutcVsbXwYVEpR8=TQDtZ8WOTCpOdy30ccO4LA27KA0-g@mail.gmail.com>

Hi,

I use ubuntu 12.4 which have gnutls-2.12 which is pretty up-to-date I think.

I tried to start openssl server instead of using apache and I get this
results:

openssl s_server -accept 444  -cert server.crt -key server.key -CAfile
ca.crt -verify required -tls1   => works with gnutls-cli

openssl s_server -accept 444  -cert server.crt -key server.key -CAfile
ca.crt -verify required -tls1_1   => works with gnutls-cli

openssl s_server -accept 444  -cert server.crt -key server.key -CAfile
ca.crt -verify required -tls1_2   => fail with gnutls-cli

Perhaps it may help to understand why it fail with apache and mod_ssl ?





2013/2/12 Nikos Mavrogiannopoulos <nmav at gnutls.org>

> On 02/11/2013 05:48 PM, Fr?d?ric Dreier wrote:
>
> > Hi,
> >
> > I try since some hours deploy a webdav server using apache under ubuntu
> > 12.4 using client certificates.
> [...]
>
> > Now I want to use davfs2 which use gnutls but it exits with an gnutls
> error (handshake failed, no details)
>
> >
> > I tried with gnutls-cli and I also get an error (with more details), but
> I
> > am not able to understand it (or what is incorrect).
> [...]
> > I only found one post refering to unimplemented SHA512 in gnutls. Is that
> > the reason?
>
>
> Hello,
>  Which version of gnutls is that? Note that many distributions have many
> years old gnutls. If this is the case, try using a recent version of
> gnutls from www.gnutls.org.
>
> regards,
> Nikos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20130212/83bfb999/attachment-0001.htm>

From nmav at gnutls.org  Tue Feb 12 12:24:43 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Tue, 12 Feb 2013 12:24:43 +0100
Subject: [gnutls-help] gnutls-cli and apache
In-Reply-To: <CAA5b1EutcVsbXwYVEpR8=TQDtZ8WOTCpOdy30ccO4LA27KA0-g@mail.gmail.com>
References: <CAA5b1Et470t2Ay0U+EJMbPMS18Q3iqhi0HYc+Y1fDXMM=tC75Q@mail.gmail.com>
	<5119FB9A.5000800@gnutls.org>
	<CAA5b1EutcVsbXwYVEpR8=TQDtZ8WOTCpOdy30ccO4LA27KA0-g@mail.gmail.com>
Message-ID: <511A267B.2080705@gnutls.org>

On 02/12/2013 10:10 AM, Fr?d?ric Dreier wrote:

> Hi,
> I use ubuntu 12.4 which have gnutls-2.12 which is pretty up-to-date I think.


2.12.x is no longer supported by me at least. Nevertheless, there have
been many releases in this branch and the latest is 2.12.23. Is it the
latest version you are using?

> Perhaps it may help to understand why it fail with apache and mod_ssl ?


I think it is more important to know if this has already been solved in
the latest version of the branch you are using, or the latest gnutls
version.

regards,
Nikos


From nmav at gnutls.org  Tue Feb 12 12:28:12 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Tue, 12 Feb 2013 12:28:12 +0100
Subject: [gnutls-help] Generating a certificate with an encrypted
 private key
In-Reply-To: <CAL=Q3eP=ATE_4SH_L91EC=dSf9du=Pu2xmuDVLktxA_xCH7Z4g@mail.gmail.com>
References: <CAL=Q3ePqwpNHXdKTbUJ+um_moRWx__v7Fs9PPfGaE968QVpEFQ@mail.gmail.com>
	<CAJU7zaLyUjJ6u_H509UEeX6B0fiLAZG2MZHNRLaHm0cbtVd15g@mail.gmail.com>
	<CAL=Q3ePXKFrekPh8M7CX9yR1ONwKASFtCBA9GbjSZA1o4FiTWA@mail.gmail.com>
	<CAJU7zaJgYDgN-XokAF8cXMHaXTPG-tdF9CuNFV3X4Kr8B8d-JQ@mail.gmail.com>
	<CAL=Q3eP=ATE_4SH_L91EC=dSf9du=Pu2xmuDVLktxA_xCH7Z4g@mail.gmail.com>
Message-ID: <511A274C.2090902@gnutls.org>

On 02/10/2013 08:18 PM, Yan Fiz wrote:

> Hello,
> 
> GnuTLS 3.1.8 can generate a certificate with an encrypted private key
> (thank you for fixing it), but cannot generate a PKCS #12 structure with
> that encrypted private key and that certificate, while GnuTLS 3.0.22 can.


It seems we're getting close though.
I've added that functionality to the repository.

regards,
Nikos



From frederic.dreier at gmail.com  Tue Feb 12 15:47:16 2013
From: frederic.dreier at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Dreier?=)
Date: Tue, 12 Feb 2013 15:47:16 +0100
Subject: [gnutls-help] gnutls-cli and apache
In-Reply-To: <511A267B.2080705@gnutls.org>
References: <CAA5b1Et470t2Ay0U+EJMbPMS18Q3iqhi0HYc+Y1fDXMM=tC75Q@mail.gmail.com>
	<5119FB9A.5000800@gnutls.org>
	<CAA5b1EutcVsbXwYVEpR8=TQDtZ8WOTCpOdy30ccO4LA27KA0-g@mail.gmail.com>
	<511A267B.2080705@gnutls.org>
Message-ID: <CAA5b1EtoTT932U9fWT31HLveWcJNn9SpjsB5sZKj-WGYdMAqJA@mail.gmail.com>

I installed gnutls 2.12.23 and it solves the problem.

Thank you very much for your help.

Best regards,

Frederic


2013/2/12 Nikos Mavrogiannopoulos <nmav at gnutls.org>

> On 02/12/2013 10:10 AM, Fr?d?ric Dreier wrote:
>
> > Hi,
> > I use ubuntu 12.4 which have gnutls-2.12 which is pretty up-to-date I
> think.
>
>
> 2.12.x is no longer supported by me at least. Nevertheless, there have
> been many releases in this branch and the latest is 2.12.23. Is it the
> latest version you are using?
>
> > Perhaps it may help to understand why it fail with apache and mod_ssl ?
>
>
> I think it is more important to know if this has already been solved in
> the latest version of the branch you are using, or the latest gnutls
> version.
>
> regards,
> Nikos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20130212/cf698f8c/attachment.htm>

From nmav at gnutls.org  Wed Feb 27 20:10:16 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Wed, 27 Feb 2013 20:10:16 +0100
Subject: [gnutls-help] gnutls 3.1.9
Message-ID: <512E5A18.9040703@gnutls.org>

Hello,
 I've just released gnutls 3.1.9. This is bug fix release on the current
stable branch.


* Version 3.1.9 (released 2013-02-27)

** certtool: Option --to-p12 will now ask for a password to generate
a PKCS #12 file from an encrypted key file. Reported by Yan Fiz.

** libgnutls: Corrected issue in gnutls_pubkey_verify_data().

** libgnutls: Corrected parsing issue in XMPP within a subject
alternative name. Reported by James Cloos.

** libgnutls: gnutls_pkcs11_reinit() will reinitialize all PKCS #11
modules, and not only the ones loaded via p11-kit.

** libgnutls: Added function to check whether the private key is
still available (inserted).

** libgnutls: Try to detect fork even during nonce generation.

** API and ABI modifications:
gnutls_handshake_set_random: Added
gnutls_transport_set_int2: Added
gnutls_transport_get_int2: Added
gnutls_transport_get_int: Added
gnutls_record_cork: Exported
gnutls_record_uncork: Exported
gnutls_pkcs11_privkey_status: Added


Getting the Software
====================

GnuTLS may be downloaded directly from
<ftp://ftp.gnutls.org/gcrypt/gnutls/>.  A list of GnuTLS mirrors can be
found at <http://www.gnutls.org/download.html>.

Here are the XZ and LZIP compressed sources:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.9.tar.xz
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.9.tar.lz

Here are OpenPGP detached signatures signed using key 0x96865171:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.9.tar.xz.sig
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.9.tar.lz.sig

Note that it has been signed with my openpgp key:
pub   3104R/96865171 2008-05-04 [expires: 2028-04-29]
uid                  Nikos Mavrogiannopoulos <nmav <at> gnutls.org>
uid                  Nikos Mavrogiannopoulos <n.mavrogiannopoulos <at>
gmail.com>
sub   2048R/9013B842 2008-05-04 [expires: 2018-05-02]
sub   2048R/1404A91D 2008-05-04 [expires: 2018-05-02]

regards,
Nikos


From nmav at gnutls.org  Thu Feb 28 08:34:16 2013
From: nmav at gnutls.org (Nikos Mavrogiannopoulos)
Date: Thu, 28 Feb 2013 08:34:16 +0100
Subject: [gnutls-help] gnutls 3.1.9
In-Reply-To: <512E5A18.9040703@gnutls.org>
References: <512E5A18.9040703@gnutls.org>
Message-ID: <512F0878.6000605@gnutls.org>

On 02/27/2013 08:10 PM, Nikos Mavrogiannopoulos wrote:

> Hello,
>  I've just released gnutls 3.1.9. This is bug fix release on the current
> stable branch.


Note that I've replaced this release with 3.1.9.1 few minutes after the
announcement. The changes were tiny to warrant a proper release, but
also important to wait for the next one (one new function wasn't
exported by LD script).

The replaced release is at:
ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/removed/

regards,
Nikos


From frederic.dreier at gmail.com  Mon Feb 11 17:23:22 2013
From: frederic.dreier at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Dreier?=)
Date: Mon, 11 Feb 2013 16:23:22 -0000
Subject: [gnutls-help] Connecting Apache with client certificates
Message-ID: <CAA5b1Euj1JGQeGQ9L-i7=CU6Ub_ro7Eh3mSEc3DOd3mZEstatw@mail.gmail.com>

Hi,

I try since some hours deploy a webdav server using apache under ubuntu
12.4 using client certificates.

I already setup apache+webdav and I can access it through firefox using the
client certificate.

Now I want to use davfs2 which use gnutls but it exits with an gnutls error
(handshake failed, no details)

I tried with gnutls-cli and I also get an error (with more details), but I
am not able to understand it (or what is incorrect).

gnutls-cli -d 9 --x509cafile ca.crt --x509keyfile client.key --x509certfile
client.crt -p 443 myserver
Processed 1 CA certificate(s).
Processed 1 client certificates...
Processed 1 client X.509 certificates...
Resolving 'myserver'...
Connecting to '192.168.1.10:443'...
|<4>| REC[0x1495a80]: Allocating epoch #0
|<2>| ASSERT: gnutls_constate.c:695
|<4>| REC[0x1495a80]: Allocating epoch #1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_AES_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_AES_128_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_CAMELLIA_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_AES_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_AES_256_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_CAMELLIA_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_RSA_3DES_EDE_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_AES_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_AES_128_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_CAMELLIA_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_AES_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_AES_256_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_CAMELLIA_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_3DES_EDE_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: DHE_DSS_ARCFOUR_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_AES_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_AES_128_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_CAMELLIA_128_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_AES_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_AES_256_CBC_SHA256
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_CAMELLIA_256_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_3DES_EDE_CBC_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_ARCFOUR_SHA1
|<3>| HSK[0x1495a80]: Keeping ciphersuite: RSA_ARCFOUR_MD5
|<2>| EXT[0x1495a80]: Sending extension SERVER NAME (19 bytes)
|<2>| EXT[0x1495a80]: Sending extension SAFE RENEGOTIATION (1 bytes)
|<2>| EXT[0x1495a80]: Sending extension SESSION TICKET (0 bytes)
|<2>| EXT[SIGA]: sent signature algo (4.2) DSA-SHA256
|<2>| EXT[SIGA]: sent signature algo (4.1) RSA-SHA256
|<2>| EXT[SIGA]: sent signature algo (2.1) RSA-SHA1
|<2>| EXT[SIGA]: sent signature algo (2.2) DSA-SHA1
|<2>| EXT[0x1495a80]: Sending extension SIGNATURE ALGORITHMS (10 bytes)
|<3>| HSK[0x1495a80]: CLIENT HELLO was sent [139 bytes]
|<4>| REC[0x1495a80]: Sending Packet[0] Handshake(22) with length: 139
|<4>| REC[0x1495a80]: Sent Packet[1] Handshake(22) with length: 144
|<4>| REC[0x1495a80]: Expected Packet[0] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[0] Alert(21) with length: 2
|<4>| REC[0x1495a80]: Decrypted Packet[0] Alert(21) with length: 2
|<4>| REC[0x1495a80]: Alert[1|112] - The server name sent was not
recognized - was received
|<2>| ASSERT: gnutls_record.c:726
|<2>| ASSERT: gnutls_record.c:1122
*** Non fatal error: A TLS warning alert has been received.
*** Received alert [112]: The server name sent was not recognized
|<4>| REC[0x1495a80]: Expected Packet[1] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[1] Handshake(22) with length: 57
|<4>| REC[0x1495a80]: Decrypted Packet[1] Handshake(22) with length: 57
|<3>| HSK[0x1495a80]: SERVER HELLO was received [57 bytes]
|<3>| HSK[0x1495a80]: Server's version: 3.3
|<3>| HSK[0x1495a80]: SessionID length: 0
|<3>| HSK[0x1495a80]: SessionID: 00
|<3>| HSK[0x1495a80]: Selected cipher suite: DHE_RSA_AES_128_CBC_SHA1
|<2>| EXT[0x1495a80]: Parsing extension 'SERVER NAME/0' (0 bytes)
|<2>| EXT[0x1495a80]: Parsing extension 'SAFE RENEGOTIATION/65281' (1 bytes)
|<2>| EXT[0x1495a80]: Parsing extension 'SESSION TICKET/35' (0 bytes)
|<3>| HSK[0x1495a80]: Safe renegotiation succeeded
|<4>| REC[0x1495a80]: Expected Packet[2] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[2] Handshake(22) with length: 2510
|<4>| REC[0x1495a80]: Decrypted Packet[2] Handshake(22) with length: 2510
|<3>| HSK[0x1495a80]: CERTIFICATE was received [2510 bytes]
|<2>| ASSERT: ext_signature.c:388
|<2>| ASSERT: ext_signature.c:388
|<2>| ASSERT: mpi.c:609
|<2>| ASSERT: dn.c:1209
|<4>| REC[0x1495a80]: Expected Packet[3] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[3] Handshake(22) with length: 527
|<4>| REC[0x1495a80]: Decrypted Packet[3] Handshake(22) with length: 527
|<3>| HSK[0x1495a80]: SERVER KEY EXCHANGE was received [527 bytes]
|<3>| HSK[0x1495a80]: verify handshake data: using RSA-SHA256
|<2>| ASSERT: ext_signature.c:388
|<4>| REC[0x1495a80]: Expected Packet[4] Handshake(22) with length: 1
|<4>| REC[0x1495a80]: Received Packet[4] Handshake(22) with length: 97
|<4>| REC[0x1495a80]: Decrypted Packet[4] Handshake(22) with length: 97
|<3>| HSK[0x1495a80]: CERTIFICATE REQUEST was received [93 bytes]
|<2>| EXT[SIGA]: rcvd signature algo (6.1) RSA-SHA512
|<2>| EXT[SIGA]: rcvd signature algo (6.2) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (6.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (5.1) RSA-SHA384
|<2>| EXT[SIGA]: rcvd signature algo (5.2) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (5.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (4.1) RSA-SHA256
|<2>| EXT[SIGA]: rcvd signature algo (4.2) DSA-SHA256
|<2>| EXT[SIGA]: rcvd signature algo (4.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (3.1) RSA-SHA224
|<2>| EXT[SIGA]: rcvd signature algo (3.2) DSA-SHA224
|<2>| EXT[SIGA]: rcvd signature algo (3.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (2.1) RSA-SHA1
|<2>| EXT[SIGA]: rcvd signature algo (2.2) DSA-SHA1
|<2>| EXT[SIGA]: rcvd signature algo (2.3) GOST R 34.10-94
|<2>| EXT[SIGA]: rcvd signature algo (1.1) RSA-MD5
|<3>| HSK[0x1495a80]: SERVER HELLO DONE was received [4 bytes]
|<3>| HSK[0x1495a80]: CERTIFICATE was sent [1137 bytes]
|<3>| HSK[0x1495a80]: CLIENT KEY EXCHANGE was sent [134 bytes]
|<2>| sign handshake cert vrfy: picked RSA-SHA512 with SHA512
|<2>| ASSERT: gnutls_sig.c:630
|<2>| ASSERT: auth_cert.c:1562
|<2>| ASSERT: gnutls_kx.c:336
|<2>| ASSERT: gnutls_handshake.c:2833
*** Fatal error: GnuTLS internal error.
|<4>| REC: Sending Alert[2|80] - Internal error
|<4>| REC[0x1495a80]: Sending Packet[1] Alert(21) with length: 2
|<4>| REC[0x1495a80]: Sent Packet[2] Alert(21) with length: 7
*** Handshake has failed
GnuTLS error: GnuTLS internal error.
|<4>| REC[0x1495a80]: Epoch #0 freed
|<4>| REC[0x1495a80]: Epoch #1 freed


Using "openssl client -connect ..." I am able to connect apache with the
client certificate and execute a GET request.

I only found one post refering to unimplemented SHA512 in gnutls. Is that
the reason?

Best regards,

Frederic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20130211/ea505f3c/attachment-0001.html>