From 27a858a504ba02df8b3647714a033f6ba06565c6 Mon Sep 17 00:00:00 2001 From: Tatsuhiro Tsujikawa Date: Wed, 17 Dec 2008 12:35:23 +0000 Subject: [PATCH] 2008-12-17 Tatsuhiro Tsujikawa Updated "How to build" section in README. Mentioned about --with-ca-bundle compile option. * README --- ChangeLog | 6 ++++++ README | 26 ++++++++++++++++++++++++-- README.html | 25 ++++++++++++++++++++++--- 3 files changed, 52 insertions(+), 5 deletions(-) diff --git a/ChangeLog b/ChangeLog index 2f6b25b2..7fa5f0f7 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2008-12-17 Tatsuhiro Tsujikawa + + Updated "How to build" section in README. Mentioned about + --with-ca-bundle compile option. + * README + 2008-12-17 Tatsuhiro Tsujikawa Bump up version number to 1.1.0. diff --git a/README b/README index 1c3be329..fc069a2a 100644 --- a/README +++ b/README @@ -108,14 +108,36 @@ You can use libexpat1-dev instead of libxml2-dev: * libexpat1-dev (Required for Metalink support) -The build process is fairly standard way for *nix programs: +The quickest way to build aria2 is just type following commands: ------------- $ ./configure $ make ------------- -The executable is aria2c in src directory. +The configure script checks available libraries and enables the features +as much as possible because all the features are enabled by default. + +Since 1.1.0, aria2 checks the certificate of HTTPS servers by default. +If you build with HTTPS support, I recommend to supply the path to the +CA bundle file. For example, in Debian the path to CA bundle file is +'/etc/ssl/certs/ca-certificates.crt' (in ca-certificates package). This +may varies depending on the distributions. You can give it to +configure script using \--with-ca-bundle option: + +------------------------------------------------------------------- +$ ./configure --with-ca-bundle='/etc/ssl/certs/ca-certificates.crt' +$ make +------------------------------------------------------------------- + +Without \--with-ca-bundle option, you will encounter the error when +accessing HTTPS servers because the certificate cannot be verified +without CA bundle. In such case, you can specify the CA bundle file +using aria2's \--ca-certificate option. If you don't have CA bundle +file installed, then the last resort is disable the certificate +validation using \--check-certificate=false. + +The executable is 'aria2c' in src directory. aria2 uses CppUnit for automated unit testing. To run run the unit test: diff --git a/README.html b/README.html index 851e9942..f78997ab 100644 --- a/README.html +++ b/README.html @@ -674,13 +674,32 @@ libexpat1-dev (Required for Metalink support)

-

The build process is fairly standard way for *nix programs:

+

The quickest way to build aria2 is just type following commands:

$ ./configure
 $ make
-

The executable is aria2c in src directory.

+

The configure script checks available libraries and enables the features +as much as possible because all the features are enabled by default.

+

Since 1.1.0, aria2 checks the certificate of HTTPS servers by default. +If you build with HTTPS support, I recommend to supply the path to the +CA bundle file. For example, in Debian the path to CA bundle file is +/etc/ssl/certs/ca-certificates.crt (in ca-certificates package). This +may varies depending on the distributions. You can give it to +configure script using --with-ca-bundle option:

+
+
+
$ ./configure --with-ca-bundle='/etc/ssl/certs/ca-certificates.crt'
+$ make
+
+

Without --with-ca-bundle option, you will encounter the error when +accessing HTTPS servers because the certificate cannot be verified +without CA bundle. In such case, you can specify the CA bundle file +using aria2's --ca-certificate option. If you don't have CA bundle +file installed, then the last resort is disable the certificate +validation using --check-certificate=false.

+

The executable is aria2c in src directory.

aria2 uses CppUnit for automated unit testing. To run run the unit test:

@@ -867,7 +886,7 @@ max-upload-limit=40K