[vlc-devel] Future of the update mechanism
remi at remlab.net
Wed Jul 29 18:31:53 CEST 2009
Le mercredi 29 juillet 2009 19:20:44 jpd at videolan.org, vous avez écrit :
> Not to say your description of the framework isn't spiffy, and
> securecryptohashcheckverificationing is pretty much required nowadays,
> should we want such a thing, but the overriding concern is not how nice
> the framework is. What should worry us first is how we present minimum
> hassle for /the user/ (including update nagging), combine that with
> minimum extra code and complexity for us, and before all else make sure
> nothing happens without /the user/'s informed consent.
Well... generally, I think (s)he who writes the code is right.
*But* in this case, we have a critical, over-used and expensive server back-
end that must be taken into account as well. I am really not very keen on
using a centralized SSL solution, not to mention that we'd have to file for
and buy x509 certificates.
More information about the vlc-devel