Reorganize C headers

aFeLiOn — Sat, 12 Jan 2013 07:23:59 -0000

Currently, all declaration of functions that used in the library is presented in the header ssl.h as it also includes tls.h. Therefore, it likely causes naming conflict in the application which uses this library.

For example, when I tried to integrate axtls with ssmtp, I got this error:
md5auth/hmac_md5.h:5:6: error: conflicting types for ‘hmac_md5’

Additionally, unnecessary header files are needed along with the release, they are config.h, os_int.h, crypto.h, crypto_misc.h...

It would be easier for user if those headers are separated into exported and internal ones.
For instance, the ssl.h does not include any internal header files and only has:

typedef struct _SSL SSL;
typedef struct _SSL_CTX SSL_CTX;

EXP_FUNC SSL_CTX * STDCALL ssl_ctx_new(uint32_t options, int num_sessions);
...

While tls.h should only be included in axtls source codes (*.c)
Please consider this issue.

Cheers

Support for configurable listening address and port

Joachim Nilsson — Mon, 29 Jun 2009 10:03:44 -0000

I would humbly like to propose adding support for run-time configurable listening address and port, for both http and https requests. Below is a possible syntax, inspired by Dropbear SSH and Net-SNMP.

axhttpd [-h 192.168.1.0:8080] [-s 199.232.41.10:443]

Or, in a /etc/axhttpd.conf file:

[http]
ListenAddress <host|IPv4_addrIPv4_addr>[:port]

[https]
ListenAddress <host|IPv4_addrIPv4_addr>[:port]

Optionally, multiple ListenAddress lines, or -h and -s arguments, could be supported. The daemon would then listen to all those listed.

If no configuration, or command line arguments exists the daemon can fall back to its default behaviour of listeing on all (IPv4?) interfaces for both http and https.

For reference, Dropbear uses the following syntax:

-p [address:]port
Listen on specified address and TCP port. If just a port is given listen on all addresses. up to 10 can be specified (default 22 if none specified).

and Net-SNMP uses: snmpd [OPTIONS] [LISTENING ADDRESSES]
Where a LISTENING ADDRESS is defined as [<transport-specifier>:]<transport-address>. In its simplest form 127.0.0.1:161, similar to Dropbear.

Recent changes to feature-requests

Reorganize C headers

Support for configurable listening address and port