package (the vulnerable ssl lib) needs to be upgraded. If a problem with
Go's SSL implementation is discovered, every Go application that might use
that library needs to be rebuilt, and for packages without source code you'd
never know which ones include the vulnerable code. He does, however, agree
that the 'single binary' deployment is an improvement over fighting with
multitudes of Perl or Python modules.
Go's SSL implementation is discovered, every Go application that might use
that library needs to be rebuilt, and for packages without source code you'd
never know which ones include the vulnerable code. He does, however, agree
that the 'single binary' deployment is an improvement over fighting with
multitudes of Perl or Python modules.
static-linked, you can update the code, recompile everything and
redeploy without much trouble, one single makefile could do that.
And, given how Go works, you could replace the wrong library with your
fixed one. Now you can have a fix at source level and fix the library
yourself if the main author aren't helpful.
and for packages without source code
Even if you are using dynamic-linked, using packages without thesource isn't "safe". You will need to trust the author's of the
package.
--
André Moraes
http://amoraes.info
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
