Skip to content
forked from gnutls/gnutls

Mirror of official gnutls repository

License

Notifications You must be signed in to change notification settings

arthenica/gnutls

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CII Best Practices

Branch CI system Status Test suite coverage Fuzzer coverage
Master/3.8.x Gitlab build status coverage report Fuzzer coverage report
Master/3.8.x Github Actions build status N/A N/A
3.7.x Gitlab build status N/A N/A
3.6.x Gitlab build status N/A N/A

GnuTLS -- Information for developers

GnuTLS implements the TLS/SSL (Transport Layer Security aka Secure Sockets Layer) protocol. Additional information can be found at www.gnutls.org.

This file contains instructions for developers and advanced users that want to build from version controlled sources. See INSTALL.md for building released versions.

We require several tools to check out and build the software, including:

The required software is typically distributed with your operating system, and the instructions for installing them differ. Here are some hints:

Debian/Ubuntu:

apt-get install -y dash git-core autoconf libtool gettext autopoint
apt-get install -y automake python3 nettle-dev libp11-kit-dev libtspi-dev libunistring-dev
apt-get install -y libtasn1-bin libtasn1-6-dev libidn2-0-dev gawk gperf
apt-get install -y libtss2-dev libunbound-dev dns-root-data bison gtk-doc-tools
apt-get install -y texinfo texlive texlive-plain-generic texlive-extra-utils

NOTE: Some software versions might not be available in older releases, e.g. nettle-dev. Available backport repos, APT-Pinning or source code compiling can be used to install these versions (and dependencies) from a newer release.

Fedora/RHEL:

yum install -y dash git autoconf libtool gettext-devel automake patch
yum install -y nettle-devel p11-kit-devel libunistring-devel
yum install -y tpm2-tss-devel trousers-devel libtasn1-devel libidn2-devel gawk gperf
yum install -y libtasn1-tools unbound-devel bison gtk-doc texinfo texlive

Sometimes, you may need to install more recent versions of Automake, Nettle, and P11-kit, which you will need to build from sources.

Dependencies that are used during make check or make dist are listed below. Moreover, for basic interoperability testing you may want to install openssl and mbedtls.

Debian/Ubuntu:

apt-get install -y valgrind nodejs softhsm2 faketime lcov libssl-dev libcmocka-dev expect libev-dev
apt-get install -y dieharder openssl abigail-tools socat net-tools ppp util-linux

NOTE: libubsan0 and libasan1 are required on older versions of Ubuntu <= 16.04. This packages must be manually added on these versions:

apt-get install -y v libubsan0 libasan1

Fedora/RHEL:

yum install -y valgrind libasan libasan-static libubsan nodejs softhsm faketime lcov openssl-devel expect libev-devel
yum install -y dieharder mbedtls-utils openssl libabigail libcmocka-devel socat util-linux

To download the version controlled sources:

$ git clone https://gitlab.com/gnutls/gnutls.git
$ cd gnutls

The next step is to bootstrap and ./configure:

$ ./bootstrap
$ ./configure

When built this way, some developer defaults will be enabled. See cfg.mk for details.

Then build the project normally, and run the test suite.

$ make
$ make check

To test the code coverage of the test suite use the following:

$ ./configure --enable-code-coverage
$ make && make check && make code-coverage-capture

Individual tests that may require additional hardware (e.g., smart cards) are:

$ sh tests/suite/testpkcs11

Building for windows

It is recommended to cross compile using Fedora and the following dependencies:

yum install -y wine mingw32-nettle mingw32-libtasn1 mingw32-gcc

and build as:

mingw32-configure --disable-non-suiteb-curves --disable-doc --without-p11-kit
mingw32-make
mingw32-make check

Continuous Integration (CI)

We utilize two continuous integration systems, the gitlab-ci and travis. Gitlab-CI is used to test most of the Linux systems (see .gitlab-ci.yml), and is split in two phases, build image creation and compilation/test. The build image creation is done at the gnutls/build-images subproject and uploads the image at the gitlab.com container registry. The compilation/test phase is on every commit to gnutls project.

The Travis based CI, is used to test compilation on MacOSX based systems.

Contributing

See the contributing document.

Happy hacking!


Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.

About

Mirror of official gnutls repository

Resources

License

Security policy

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C 77.5%
  • Assembly 15.9%
  • Shell 4.1%
  • Makefile 0.8%
  • HTML 0.6%
  • M4 0.6%
  • Other 0.5%