On Mon, Jul 21, 2014 at 2:52 AM, Marcus Meissner <meissner@suse.de> wrote:
On Mon, Jul 21, 2014 at 07:24:39AM +0200, Mathias Homann wrote:
On 21. Juli 2014 07:14:53 MESZ, Michal Kubecek <mkubecek@suse.cz> wrote:
No doubt forcing LibreSSL on users as the only option would be bad idea. But so is forcing LibreSSL out of the distribution just because of some "one tool per task" doctrine.
+1, but can we actually give people the choice here? Technically, I mean... anything that uses encryption has to be linked against one of the choices, and then can't just use "the other ssl" without recompiling, right?
Not right now, no.
But people would now be able to build against libressl in their projects without funny linking.
At least postgres' next versions are trying to support multiple implementations. Not with libressl in mind, it's more about using window's native SSL implementation, but I bet that can make supporting libressl in postgres easy. But unless libressl is ABI-compatible with openssl (which might be the case for now?) I think its application may be limited to those that explicitly support switching between ssl implementations. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org