[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] Config file parsing

From: Blake Matheny
Subject: Re: [GNUnet-developers] Config file parsing
Date: Mon, 1 Jul 2002 00:03:26 -0500
User-agent: Mutt/1.3.99i

GNUnet is a framework for anonymous encrypted networking. Because of this, in
most cases the more configurable GNUnet can be, the better. I would be up for
using gnutls, assuming a couple of things. Obviously complete compatibility
between gnutls and openssl is a must. Look into the cryptographic functions
that GNUnet takes advantage of, and make sure that gnutls already has those
before you bother writing any code.  I also see that it falls under the LGPL
and not the GPL. I don't think that's an issue, but anyone know what the
difference is?


Whatchu talkin' 'bout, Willis?
> I would like make gnunet compilable against gnutls instead of openssl,
> however currently gnunet uses openssl ANS1 functions to parse its config
> file.
> I would like to seperate the config file parsing functions from the ssl
> library, i was prepared to write custom config file parsing code, however
> looking around i found the dot.conf library, which does everything needed.
> The major difference would be that libdotconf uses apache style config
> file, which doesnt use an equals sign to seperate the field name from its
> field value, just whitespace.
> I think its good to use small (libdotconf is 17kB) specific libraries such
> as this, code re-use etc.
> I have made a standalone app that demonstrates (in part) how libdotconf
> could be used with gnunet, it provides the same external functions from
> configuration.c does, so it should drop in easily, its at
> If there arent any major objections to the idea i will work on a patch for
> GNUnet, but i would appreciate a bit of feedback before i take it much
> further incase im wasting my time.
> Glenn
> _______________________________________________
> GNUnet-developers mailing list
> address@hidden

Blake Matheny

reply via email to

[Prev in Thread] Current Thread [Next in Thread]