by having interfaces in C, we still get multi-language support too. (would love to see this for encryption)
-
-
Replying to @hergertme @federicomena and
@BRIAN_____'s *ring* started as a fork of BoringSSL, but I don't know if it maintained C API compat.1 reply 0 retweets 0 likes -
Replying to @TedMielczarek @hergertme and
I started an OpenSSL-API-compatible thing but haven't found anybody interested in it.
3 replies 0 retweets 0 likes -
Replying to @BRIAN_____ @TedMielczarek and
pluggable TLS backends in glib-networking (due to licensing constraints). maybe there?
2 replies 0 retweets 0 likes -
Replying to @hergertme @TedMielczarek and
But, are pluggable APIs really necessary? Lots of complexity is added for pluggability.
1 reply 0 retweets 0 likes -
Replying to @BRIAN_____ @TedMielczarek and
we can't link statically or even dynamically for licensing reasons.
1 reply 0 retweets 0 likes -
Replying to @hergertme @BRIAN_____ and
say you want FIPS, requires certain openssl. or gnutls which has other license restrictions
1 reply 0 retweets 0 likes -
Replying to @hergertme @TedMielczarek and
What license would be acceptable for all scenerios(disregarding FIPS for a moment)?
1 reply 0 retweets 0 likes -
-
Replying to @BRIAN_____ @TedMielczarek and
we are LGPL-2.1+, so anything compatible with that.
1 reply 0 retweets 0 likes
What's the project's policy on Rust? Are core components (not plug-ins) in Rust acceptable?
-
-
Replying to @BRIAN_____ @TedMielczarek and
very interested in Rust from GNOME-land. But you would be pioneering. (And we need that)
0 replies 1 retweet 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.