other crypto apis

[Lorenz Schori]

Hi

I'd like to make tincd work with other crypto apis than openssl/ 
libcrypt. I've learned from the subversion repository that an effort  
was started to port it to gnu-tls. I for myself would like to get  
tincd linking against xyssl (1) because it is very lightweight and  
thus an adequate option on devices with little memory and disk/flash  
space, i.e. embedded systems. Now i'm browsing the sourcecode from  
1.1 branch and i'm tempted to isolate everything which is looking  
like crypto stuff to a separate file and defining some wrapper  
functions resulting in an abstraction layer.

 From 2.0 README i learn that openssl should be dropped in favour of  
gnutls and gnucrypt. I think this might be a good chance to  
modularize this part of tinc, so poeple/distributors may choose from  
different crypto/auth backends.

Now my two questions:
- Is it worth investing a great effort into tinc 1.1 and create some  
abstraction layer?
- Any chances to get something like this into 2.0? Is this branch  
already in active development or is it a still stub?

Cheers,
Lorenz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20070902/b062c2fe/attachment.pgp