gmane.network.gnutls.general

gnutls 3.2.0

Nikos Mavrogiannopoulos — 2013-05-10T16:38:45

Hello,
 I've just released gnutls 3.2.0. This release significantly
improves the performance of gnutls in two ways. The new elliptic curve
implementation of nettle 2.7 is used which improves performance by a
factor of 2 (thanks to Niels Moeller), and on the ciphersuite level
the (currently) private ciphersuites with Salsa20 and UMAC-96 are
defined, giving a performance boost compared to any ARCFOUR or AES 
based ciphersuites. The new ciphersuites also provide a solution to the
recent attacks in TLS that compromise the security of CBC-based
ciphersuites and ARCFOUR. Note that since these are private --i.e.,
gnutls-specific-- ciphersuites they are not enabled by default.

In addition on this release all support for the so-called EXPORT
ciphersuites is dropped.


* Version 3.2.0 (released 2013-05-10)

** libgnutls: Use nettle's elliptic curve implementation.

** libgnutls: Added Salsa20 cipher

** libgnutls: Added UMAC-96 and UMAC-128

** libgnutls: Added ciphersuites involving Salsa20 and UMAC-96.
As they are not standardized they are defined using private ciphersuite 
numbers.

** libgnutls: Added support for DTLS 1.2.

** libgnutls: Added support for the Application Layer Protocol
Negotiation (ALPN) extension.

** libgnutls: Removed support for the RSA-EXPORT ciphersuites.

** libgnutls: Avoid linking to librt (that also avoids unnecessary
linking to pthreads if p11-kit isn't used).

** API and ABI modifications:
gnutls_cipher_get_iv_size: Added
gnutls_hmac_set_nonce: Added
gnutls_mac_get_nonce_size: 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.2/gnutls-3.2.0.tar.xz
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.2/gnutls-3.2.0.tar.lz

Here are OpenPGP detached signatures signed using key 0x96865171:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.2/gnutls-3.2.0.tar.xz.sig
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.2/gnutls-3.2.0.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

gnutls 3.1.11

Nikos Mavrogiannopoulos — 2013-05-10T09:45:42

Hello,
 I've just released gnutls 3.1.11. This release adds new features and
fixed bugs on the current stable branch. 

* Version 3.1.11 (released 2013-05-10)

** libgnutls: Added priority string VERS-DTLS-ALL.

** libgnutls: When in compatibility mode allow for a wrong version in
the RSA PMS.

** libgnutls: Corrected issues in DTLS heartbeat parsing. Reported by
Joke de Buhr.

** libgnutls: Heartbeat support is enabled by default.

** libgnutls: Added GNUTLS_PRIVKEY_SIGN_FLAG_TLS1_RSA which allows 
gnutls_privkey_sign_hash() to operate as with
gnutls_privkey_sign_raw_data(). This makes it consistent with
verification with GNUTLS_PUBKEY_VERIFY_FLAG_TLS1_RSA flag.

** libgnutls: Fixes in unknown DN string printing. Issues reported and
patches by Stef Walter.

** certtool: When generating certificates the default answer for
marking the key for signing and encryption is yes.

** API and ABI modifications:
gnutls_certificate_set_x509_key_mem2: Added
gnutls_certificate_set_x509_key_file2: Added
gnutls_sign_algorithm_get_client: Added
GNUTLS_PRIVKEY_SIGN_FLAG_TLS1_RSA: 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.11.tar.xz
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.11.tar.lz

Here are OpenPGP detached signatures signed using key 0x96865171:

  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.11.tar.xz.sig
  ftp://ftp.gnutls.org/gcrypt/gnutls/v3.1/gnutls-3.1.11.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

Re: Connecting Apache with client certificates

Frédéric Dreier — 2013-05-02T21:38:11

Hi,

Actually you answer me the 12 feb already :-) and you were right: updating
gnutls solved this problem.

Best regards,

Frederic


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

_______________________________________________
Gnutls-help mailing list
Gnutls-help< at >lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-help

Re: can't find libnettle

Nikos Mavrogiannopoulos — 2013-05-02T19:30:23

You should check config.log for the actual error.

regards,
Nikos

Re: Signature scheme for RSA signatures usinggnutls_x509_crt_sign2

Nikos Mavrogiannopoulos — 2013-05-02T19:31:40

Hello,
 Only RSASSA-PKCS1-V1_5 is supported. Since this is the version used
in all TLS versions there isn't much of an incentive to change that.

regards,
Nikos

_______________________________________________
Gnutls-help mailing list
Gnutls-help< at >lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-help

Re: about SSL VPN

Nikos Mavrogiannopoulos — 2013-05-02T19:29:39

The term SSL VPN is often used by marketing departments to describe
totally different technologies. The closest protocol to that term is
CISCO's SSL VPN and there is the openconnect client and server
implementations at:
http://www.infradead.org/ocserv/
http://www.infradead.org/openconnect/

regards,
Nikos

Re: Connecting Apache with client certificates

Nikos Mavrogiannopoulos — 2013-05-02T19:25:57

On Mon, Feb 11, 2013 at 5:44 PM, Frédéric Dreier
<frederic.dreier< at >gmail.com> wrote:

Hello,
 Sorry for the late reply, it seems several posts were held by the
mailing list and I missed them.


Not really. The issue looks like a bug in old gnutls versions. Should
you use a recent gnutls versions you wouldn't have the issue.

regards,
Nikos

_______________________________________________
Gnutls-help mailing list
Gnutls-help< at >lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-help

Signature scheme for RSA signatures usinggnutls_x509_crt_sign2

René Korthaus — 2013-04-16T13:19:13

Hi,

I need to know which signature scheme for RSA signatures from PKCS#1
v2.1 is used when signing a certificate using gnutls_x509_crt_sign2.
Unfortunately, I couldn't find an answer through source code analysis.
From the Google Summer of Code page (http://gnutls.org/soc.html) it
seems that RSASSA-PSS is not yet supported and RSASSA-PKCS1-V1_5 is
currently used. Is this information still accurate?

Best regards,
René

can't find libnettle

Shahar Barak — 2013-04-11T17:24:38

Hi,

When I run ./configure I get the following error:
checking for libnettle... no
configure: error:
  ***
  *** Libnettle 2.5 was not found. Note that you must compile nettle with
gmp support.

Even though I have libnettle. It is in:
/usr/local/lib/libnettle.a

Please help. I'm a novice in these things.


Thanks,

Shahar
_______________________________________________
Gnutls-help mailing list
Gnutls-help< at >lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-help

about SSL VPN

Austin — 2013-04-09T02:58:12

Hello,

 

I want to find library (SSL VPN) for my company.

Could any products support SSL VPN which the function like openVPN?

 

If support this function, please contact to me.

Thanks

 

Austin Chi 
R&D Engineer 
Advance Multimedia Internet Technology Inc. 
+886-6-5058026 Ext. 630 
Skype: austin.chi.amit.com.tw

 

_______________________________________________
Gnutls-help mailing list
Gnutls-help< at >lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-help

Connecting Apache with client certificates

Frédéric Dreier — 2013-02-11T15:44:00

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
_______________________________________________
Gnutls-help mailing list
Gnutls-help< at >lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-help

Compiling example programs

Marcel Wijnen — 2013-01-17T13:28:43

Hi All,

Currently I'm looking at the different examples that are available on the
website.When I try to compile the example code several errors appear.

In 9.1.1 Simple client example with X.509 certificate support
(
https://www.gnu.org/software/gnutls/manual/html_node/Simple-client-example-with-X_002e509-certificate-support.html#Simple-client-example-with-X_002e509-certificate-support
 )

#include "example.h" causes the error : No such file or directory

In 9.1.3 Simple client example with anonymous authentication
(
https://www.gnu.org/software/gnutls/manual/html_node/Simple-client-example-with-anonymous-authentication.html#Simple-client-example-with-anonymous-authentication
 )

undefined reference to 'tcp_connect'
undefined reference to 'gnutls_handshake_set_timeout'
undefined reference to 'tcp_close'

I'm compiling with: *gcc <filename>.c -l gnutls*

I was wondering whether someone can point me in the right direction to move
forward.

Any help is greatly appreciated. Thanks in advance.

Best,
Marcel
_______________________________________________
Gnutls-help mailing list
Gnutls-help< at >lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-help

Re: Support for via quadcore SHA512 hw acceleration

Nikos Mavrogiannopoulos — 2013-04-21T10:22:13

On Sat, Apr 20, 2013 at 10:23 PM, Daniel Kahn Gillmor
<dkg< at >fifthhorseman.net> wrote:

Unfortunately that is not the case, even though I'd prefer that :(
Nettle does not provide accelerated code for AES-NI and via padlock,
thus that is currently done in gnutls.

regards,
Nikos

Re: Support for via quadcore SHA512 hw acceleration

Nikos Mavrogiannopoulos — 2013-04-21T10:20:32

Hello Shaun,
 I am not aware of this kind of CPUs. Do they use similar instructions
and detection as in nano? If yes, the current detection mechanism is
in lib/accelerated/x86/aes-padlock.c in check_phe_sha512() function.
It could be that a different capability bit is now enabled.

regards,
Nikos

Re: Support for via quadcore SHA512 hw acceleration

Daniel Kahn Gillmor — 2013-04-20T19:23:21

I suggest following up on the nettle mailing list about this; gnutls
should be able to use whatever acceleration nettle can provide:

  Nettle Crypto Library <nettle-bugs< at >lists.lysator.liu.se>

hth,

--dkg

_______________________________________________
Gnutls-help mailing list
Gnutls-help< at >lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-help

Support for via quadcore SHA512 hw acceleration

Shaun Murphy — 2013-04-20T17:48:16

The limited literature for the newer VIA QuadCore E-Series embedded platform says that it now supports "Secure Hash Algorithm: SHA-1, SHA-256, SHA-384, SHA-512" but I'm not seeing any acceleration for SHA512 in the kernel modules or gnutls. I would appreciate some pointers on what I need to do to access that SHA512 acceleration in gnutls.
Here's my setup:Via Artigo A1250 Ubuntu 12.04 x86_64Gnutls - built from git (built nettle from source, everything else installed from apt)Kernel modules: padlock_aes, padlock_sha
Here's my dmesg output for the loaded modules:[    2.345061] padlock_aes: Using VIA PadLock ACE for AES algorithm.[    2.364105] padlock_sha: Using VIA PadLock ACE for SHA1/SHA256 algorithms.
Benchmark Soft Ciphers:Checking SHA1 (16kb payload)...  Processed 464.73 MB in 5.00 secs: 92.95 MB/secChecking SHA256 (16kb payload)...  Processed 180.04 MB in 5.00 secs: 36.01 MB/secChecking SHA512 (16kb payload)...  Processed 267.39 MB in 5.00 secs: 53.48 MB/sec
Benchmark Ciphers:Checking SHA1 (16kb payload)...  Processed 1.51 GB in 5.00 secs: 0.30 GB/secChecking SHA256 (16kb payload)...  Processed 1.30 GB in 5.00 secs: 0.26 GB/secChecking SHA512 (16kb payload)...  Processed 267.45 MB in 5.00 secs: 53.49 MB/sec
The SHA256 numbers are great but I really need SHA512 for my application.
Thank you.

       _______________________________________________
Gnutls-help mailing list
Gnutls-help< at >lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-help

Re: gnutls_certificate_set_x509_trust_file and Cygwin

Alexander Ausserstorfer — 2013-04-20T06:03:51

Zitat von Alexander Ausserstorfer <bavariasound< at >chiemgau-net.de>:


Yesterday the staff kicked me out the computer room, and today the  
wireless network access here doesn't work, so sorry for the  
circumstances.

The first question is if I use the right certificates. The file  
ca-bundle.trust.crt at cygwin/usr/ssl/certs/ sais:

############################################################################

This is a bundle of X.509 certificates of public Certificate  
Authorities. It was generated from the Mozilla root CA list. These  
certificates are in the OpenSSL "TRUSTED CERTIFICATE" format and have  
trust bits accordingly.

Source: mozilla/security/nss/lib/ckfw/builtins/certdata.txt

[...]

############################################################################

Then I use the function

gnutls_certificate_set_x509_trust_file (cert_cred, CAFILE,  
GNUTLS_X509_FMT_PEM)

to add the list but the function returns zero. It is the first time I  
try GnuTLS. It seems to me that the function does nothing. I work with  
Cygwin. May be Cygwin is the problem?

Here is all the code I wrote (I hope copy & paste work here correctly):

#ifdef HAVE_CONFIG_H
#include <config.h>
#endif

#include <stdio.h>
#include <stdlib.h>
#include <sys/socket.h> // AF_INET, SOCK_STREAM, connect()
#include <netdb.h>      // struct hostent
#include <netinet/in.h> // struct sockadd_in
#include <gnutls/gnutls.h>
#include <gnutls/x509.h>
#include <string.h>

#define MAX_BUF 1024
#define MAXMSG 512
#define CAFILE "/usr/ssl/certs/ca-bundle.trust.crt"

struct hostent *hostinfo;
struct sockaddr_in name;

static int _verify_certificate_callback (gnutls_session_t session);

void IP_number(struct sockaddr_in *name, char *servername, uint16_t port)
{
  char serverIP[16];
  if(hostinfo=gethostbyname(servername))
  {
   // converting name in IP number
   inet_ntop(PF_INET,hostinfo->h_addr_list[0],serverIP,16);
   printf("IP: %s\n",serverIP);
   name->sin_family = PF_INET;
   name->sin_port = htons(port);
   name->sin_addr = *(struct in_addr *) hostinfo->h_addr;
  }
   else
    {
      fprintf(stderr, "Unknown host %s.\n",servername);
      exit (EXIT_FAILURE);
    }
}

main()
{
  int ret, sd, ii;

  gnutls_session_t session;
  gnutls_srp_client_credentials_t srp_cred;
  gnutls_certificate_credentials_t cert_cred;

  char buffer2[MAX_BUF + 1];
  const char *err;

  // Required data
  char server[30];
  printf("Server: ");
  scanf("%s",server);

  char USER[30]="";
  printf("User: ");
  scanf("%s",USER);

  char *password;
  password=(char *)getpass("Password: ");

  char buffer[MAXMSG];
  uint16_t port=110;
  int sock=-1;
  size_t size;

  // converting server name in IP number
  IP_number(&name, server, port);

  // Creating socket for connection to this server
  sock = socket(AF_INET, SOCK_STREAM, 0);
  if (sock == -1)
  {
   perror("socket");
   exit (EXIT_FAILURE);
  }

  // Making the connection
  if (connect(sock, (struct sockaddr *) &name, sizeof (struct  
sockaddr_in)) < 0)
  {
   perror ("connect");
   exit (EXIT_FAILURE);
  }

  // Reading
  int amount = read(sock, buffer, MAXMSG);
  printf("%.*s", amount, buffer);
  write(sock,"CAPA\r\n",6);
  amount = read(sock, buffer, MAXMSG);
  printf("%.*s", amount, buffer);
  write(sock,"STLS\r\n",6);
  amount = read(sock, buffer, MAXMSG);
  printf("%.*s", amount, buffer);

// Security connection

gnutls_global_init();

gnutls_srp_allocate_client_credentials (&srp_cred);
gnutls_certificate_allocate_credentials (&cert_cred);
printf("\nAnzahl der verarbeiteten Zertifikate:  
%d\n",gnutls_certificate_set_x509_trust_file (cert_cred, CAFILE,  
GNUTLS_X509_FMT_PEM));
gnutls_certificate_set_verify_function (cert_cred,  
_verify_certificate_callback);
gnutls_srp_set_client_credentials (srp_cred, USER, password);

gnutls_init (&session, GNUTLS_CLIENT);

gnutls_session_set_ptr (session, (void *) server);
gnutls_server_name_set (session, GNUTLS_NAME_DNS, server, strlen(server));

/* Use default priorities */
ret = gnutls_priority_set_direct (session,  
"NORMAL:+SRP:+SRP-RSA:+SRP-DSS", &err);
if (ret < 0)
   {
      if (ret == GNUTLS_E_INVALID_REQUEST)
    {
   fprintf (stderr, "Syntax error at: %s\n", err);
}
 exit(1);
   }

gnutls_credentials_set (session, GNUTLS_CRD_SRP, srp_cred);
gnutls_credentials_set (session, GNUTLS_CRD_CERTIFICATE, cert_cred);
gnutls_transport_set_ptr (session, (gnutls_transport_ptr_t) sock);

do
    {
      ret = gnutls_handshake (session);
    } while (ret < 00 && gnutls_error_is_fatal (ret) == 0);

if (ret < 0)
{
  fprintf (stderr, "*** Handshake failed\n");
  gnutls_perror (ret);
  goto end;
}
else
{
  printf ("- Handshake was completed\n");
}

gnutls_record_send(session, "USER ########\r\n",15);
ret = gnutls_record_recv(session,buffer2,MAX_BUF);
  if (gnutls_error_is_fatal (ret) != 0 || ret == 0)
  {
    if (ret == 0)
      {
   printf ("- Peer has closed the GnuTLS connection\n");
   goto end;
 }
else
 {
   fprintf (stderr, "*** Error: %s\n", gnutls_strerror (ret));
   goto end;
 }
  }

     if (ret > 0)
 {
   printf ("- Reveived %d bytes: ", ret);
  for (ii = 0 ; ii < ret; ii++)
   {
    fputc (buffer2[ii], stdout);
   }
       fputs ("\n", stdout);
    }

gnutls_record_send(session, "PASS ########\r\n",15);
ret = gnutls_record_recv(session,buffer2,MAX_BUF);
  if (gnutls_error_is_fatal (ret) != 0 || ret == 0)
  {
    if (ret == 0)
      {
   printf ("- Peer has closed the GnuTLS connection\n");
   goto end;
 }
else
 {
   fprintf (stderr, "*** Error: %s\n", gnutls_strerror (ret));
   goto end;
 }
  }

     if (ret > 0)
 {
   printf ("- Reveived %d bytes: ", ret);
  for (ii = 0 ; ii < ret; ii++)
   {
    fputc (buffer2[ii], stdout);
   }
       fputs ("\n", stdout);
    }

gnutls_record_send(session, "RETR 1\r\n",8);
ret = gnutls_record_recv(session,buffer2,MAX_BUF);
  if (gnutls_error_is_fatal (ret) != 0 || ret == 0)
  {
    if (ret == 0)
      {
   printf ("- Peer has closed the GnuTLS connection\n");
   goto end;
 }
else
 {
   fprintf (stderr, "*** Error: %s\n", gnutls_strerror (ret));
   goto end;
 }
  }

     if (ret > 0)
 {
   printf ("- Reveived %d bytes: ", ret);
  for (ii = 0 ; ii < ret; ii++)
   {
    fputc (buffer2[ii], stdout);
   }
       fputs ("\n", stdout);
    }


   gnutls_bye (session, GNUTLS_SHUT_RDWR);

end:

  // Closing socket
  close(sock);

  gnutls_deinit(session);

  gnutls_srp_free_client_credentials (srp_cred);
  gnutls_certificate_free_credentials (cert_cred);

  gnutls_global_deinit();

  printf("Ready\n");

}

static int _verify_certificate_callback (gnutls_session_t session)
{
     unsigned int status;
const gnutls_datum_t *cert_list;
unsigned int cert_list_size;
int ret;
gnutls_x509_crt_t cert;
const char *hostname;

/* read hostname */
hostname = gnutls_session_get_ptr (session);

/* This varification function uses the trusted CAs in the credentials
 * structure. So you must have installed one or more CA certificates.
*/

ret = gnutls_certificate_verify_peers2 (session, &status);
if (ret < 0)
  {
    printf ("Error\n");
return GNUTLS_E_CERTIFICATE_ERROR;
       }

if (status & GNUTLS_CERT_SIGNER_NOT_FOUND)
  printf ("The certificate hasn't got a known issuer\n");

if (status & GNUTLS_CERT_REVOKED)
  printf ("The certificate has been revoked\n");

if (status & GNUTLS_CERT_EXPIRED)
       printf ("The certificate has expired\n");

     if (status & GNUTLS_CERT_NOT_ACTIVATED)
       printf ("The certificate is not yet activated\n");

     if (status & GNUTLS_CERT_INVALID)
       {
         printf ("The certificate is not trusted\n");
         return GNUTLS_E_CERTIFICATE_ERROR;
       }

     /* Up to here the process is the same for X.509 certificates and
      * OpenPGP keys. From now on X.509 certificates are assumed. This can
      * be easily extended to work with openpgp keys as well.
     */

     if (gnutls_certificate_type_get (session) != GNUTLS_CRT_X509)
       return GNUTLS_E_CERTIFICATE_ERROR;

     if (gnutls_x509_crt_init (&cert) < 0 )
       {
        printf ("error in initialization\n");
        return GNUTLS_E_CERTIFICATE_ERROR;
       }

     cert_list = gnutls_certificate_get_peers (session, &cert_list_size);
     if (cert_list == NULL)
       {
         printf ("No certificate was found!\n");
         return GNUTLS_E_CERTIFICATE_ERROR;
       }

     if (gnutls_x509_crt_import (cert, &cert_list[0], GNUTLS_X509_FMT_DER) < 0)
        {
          printf ("error parsing certificate\n");
          return GNUTLS_E_CERTIFICATE_ERROR;
        }

      if (!gnutls_x509_crt_check_hostname (cert, hostname))
        {
          printf ("The certificate's owner does not match hostname  
'%s'\n", hostname);
 return GNUTLS_E_CERTIFICATE_ERROR;
   }

gnutls_x509_crt_deinit (cert);

/* notify gnutls to continue handshake normally */
     return 0;
}

Some sensible data were replaced by ########. Thanks for any help / hints.

Alex'

gnutls_certificate_set_x509_trust_file and Cygwin

Alexander Ausserstorfer — 2013-04-19T08:10:08

Under Cygwin I set gnutls_certificate_set_x509_trust_file to

#define CAFILE "/usr/ssl/certs/ca-bundle.trust.crt"

gnutls_certificate_set_x509_trust_file (cert_cret, CAFILE,  
GNUTLS_X509_FMT_PEM);

ca-bundle.trust.crt was part of Cygwin. Now, the function  
gnutls_certificate_set_x509_trust_file returns 0 and all later  
verification of certificates fails. I suppose that the function should  
return another number as 0. Is that mind right?

A.

Corrupted data when reading from gnutls input buffer

2013-04-18T17:49:57

Hello,

I am developing a software using gnutls 3.1.0 and got a little problem,
which I hope somebody can help me get rid of.

On client side I am using a non-blocking socket and to check it for 
read readiness
I call "gnutls_record_check_pending" to see if there is data in the 
input buffer
remaining from the last read process. If not I call "select" on the 
socket to
see if data is available to be read by "gnutls_record_recv".

Every time when data is read from the internal input buffer of gnutls
I get corrupted data.

It seems to be sporadically that data is read into the input buffer of 
gnutls,
and varies in size.

Here some code:

bool Client::readable(uint32_t ms)
{
     // check for data to be read from the gnutls input buffer

     uint32_t r = gnutls_record_check_pending(m_session);

     if (r > 0) {

         return true;
     }

     // check for socket read readiness

     fd_set fds;
     FD_ZERO(&fds);
     FD_SET(m_socket, &fds);

     struct timeval tv;
     tv.tv_sec = 0;
     tv.tv_usec = ms * 1000;

     int res = select(m_socket+1, &fds, NULL, NULL, &tv);

     if (res <= 0) {

         return false;
     }

     return true;
}

uint32_t Client::recv(uint8_t* data, uint32_t size)
{
     uint32_t s = 0;

     while (s < size) {

     // wait for read readiness

     if (!readable(200)) {

         continue;
     }

     // read data

         int32_t ret = gnutls_record_recv(m_session, &data[s], size - 
s);

         if (gnutls_error_is_fatal(ret) != 0 || ret == 0) {

             if (ret == 0) {

                 return 0;
             }
             else {

                 std::cerr << "Error: " << gnutls_strerror(ret) << "\n";

                 return ret;
             }
         }

         if (ret == GNUTLS_E_INTERRUPTED || ret == GNUTLS_E_AGAIN) {

             continue;
         }

         s += ret;
     }

     return s;
}

Hope somebody can give me a hint what I may be doing wrong.

Thanks in advance.

Marc

Get cipher used to encrypt key

MK — 2013-04-17T20:39:45

This is derived from my previous problem with a password encrypted key
but does not rely upon it.  The context is, I have a password encrypted
private key for which I have the password, and gnutls (certtool, etc.)
will read it (eg. via gnutls_x509_privkey_import2()).  I would
like to find out what cipher was used to encrypt the key; the gnutls
functions "auto-detect" the format, but do not report it. If I read it
with "certtool -k -V", there is information about what public key
encryption scheme this key is for:

Public Key Info:
Public Key Algorithm: RSA
Key Security Level: Legacy (2048 bits)

But not how the key itself was encrypted with a password.  "openssl rsa"
similarly will decrypt and print information about the key, but not
the cipher it was encrypted with.  It seems to me this is useful
information that has no reason to be secret if I have the password
anyway.  For example, if someone else is using my software and
complains their key doesn't work, but doesn't know or can't remember
the cipher used, it would be nice to have a commonplace tool (such as
certtool) that I could refer them to ("Find out via certtool what form
of password encryption is used.").

I am pretty ignorant about all this, so hopefully my question makes
sense.

Sincerely, MK.

Re: confusion regarding private key encryption

Nikos Mavrogiannopoulos — 2013-04-17T15:09:23

Did you use gnutls_global_init()?

regards,
Nikos