version bump

CMakeLists.txt

@@ -10,7 +10,7 @@ else ()
   set (CMAKE_C_STANDARD 99)
 endif ()
 
-set(VERSION 0.2.0)
+set(VERSION 0.2.1)
 
 option(DEBUG              "compile with debug symbol"    OFF)
 option(BUNDLE_CIVETWEB    "bundle civetweb with uts-server"    OFF)

ChangeLog.rst

@@ -1,6 +1,11 @@
 Changelogs
 ==========
 
+0.2.1
+-----
+
+* [fix ] fix compilation for newer GCC (>10.2) (global variable definition issue 
+
 0.2.0
 -----
 

README.rst

@@ -23,10 +23,15 @@ Micro `RFC 3161 Time-Stamp <https://www.ietf.org/rfc/rfc3161.txt>`_ server writt
 :Doc:    `Uts-Server documentation on ReadTheDoc <http://uts-server.readthedocs.org/en/latest/>`_
 :Dev:    `Uts-Server source code on GitHub <https://github.com/kakwa/uts-server>`_
 :License: MIT
-:Author:  Pierre-Francois Carpentier - copyright © 2016
+:Author:  Pierre-Francois Carpentier - copyright © 2019
 
 ----
 
+Demo
+----
+
+A demo is accessible here: https://uts-server.kakwalab.ovh/
+
 License
 -------
 
@@ -45,7 +50,7 @@ Roughly, it works as follow:
 
 Then a client can verify the piece of data with the time-stamp using the Certificate Authority of the time-stamp key pair (X509 certificates).
 
-It gives a cryptographic proof of a piece of data content, like a file, at a given time.
+It gives a cryptographic proof of a piece of data content, for example a file, at a given time.
 
 Some use cases:
 
@@ -55,7 +60,7 @@ Some use cases:
 Quick (and dirty) Testing
 -------------------------
 
-Here a few steps to quickly trying out uts-server, for production setup, please compile civetweb externally and create proper CA and certificates:
+Here a few steps to quickly try out uts-server, for production setup, please compile civetweb externally and create proper CA and certificates:
 
 .. sourcecode:: bash
 

inc/utils.h

@@ -18,7 +18,3 @@ int set_params(rfc3161_context *ct, char *conf_file, char *conf_wd);
 static char *rand_string(char *str, size_t size);
 void free_uts_context(rfc3161_context *ct);
 const char *null_undef(const char *in);
-
-// some global variable to handle signals
-int g_uts_sig_up;
-int g_uts_sig;

src/lib/http.c

@@ -9,6 +9,9 @@
 #include <time.h>
 #include <unistd.h>
 
+extern int g_uts_sig_up;
+extern int g_uts_sig;
+
 static char *rand_string(char *str, size_t size) {
     const char charset[] = "1234567890ABCDEF";
     if (size) {

src/lib/rfc3161.c

@@ -269,7 +269,7 @@ end:
         BN_free(serial_bn);
     } else {
         serial_hex = calloc(SERIAL_ID_SIZE, sizeof(char));
-        strncpy(serial_hex, " NO ID   ", SERIAL_ID_SIZE + 2);
+        strncpy(serial_hex, " NO ID   ", SERIAL_ID_SIZE + 4);
     }
 #endif
 #ifdef OPENSSL_API_1_0

src/lib/utils.c

@@ -12,6 +12,10 @@
 #include <syslog.h>
 #include <unistd.h>
 
+// some global variable to handle signals
+int g_uts_sig_up;
+int g_uts_sig;
+
 static void signal_handler_general(int sig_num) {
     g_uts_sig = sig_num;
 }