Installing binaries in ~/.dropbox-dist/ of each user and letting any
user process update them there is certainly not a good choice from a
security point of view (and it's certainly not in line with the Debian
policy). Having a single way to install the binary system-wide and
having that mechanism v
So, this package appears to download binary bits directly from Dropbox
upon installation. Those binary bits will never get updated again in the
future once the package is installed, which would prevent them from
getting possible security fixes once this package is installed.
>From a security point
Hi Raphael,
I wasn't privy to the private discussion but as a Dropbox user I am why
wondering why we would turn off auto update when the software itself
depends on being updated on the user's machine by upstream. For example
what happens in the case of a security update?
--
You received this bug
Hello David,
this bug is in total contradiction to what you and Rian assured me by
private mail: “In any case, I want to stress that you can distribute
this package however you like for the Debian community. The Debian
community has their own way of thinking about problems and we just
differ here.
