I understand the differences, but it wasn't clear to me whether it "encrypted the files" for transfer only or it actually "encrypted the files" and stored them on the server that way.
Anthony On Sun, Apr 25, 2010 at 4:56 AM, Frederik Nnaji <[email protected]> wrote: > Semantically, "encrypt" means a one way street. > Only decryption can resolve the protection. > > Once a program offers to encrypt your data, it suggests nothing less. > > Browsers inform about an encrypted connection, that's a completely different > thing and would be totally misinforming, if formulated as "encrypt my > files". > > The question here lies in whether the transmission should ask the server to > encrypt, or we encrypt data locally and simply append to the already > encrypted remote file.. > > > > -- Sent from my Palm Pre > ________________________________ > On 25.04.2010 06:02, Anthony Ettinger <[email protected]> wrote: > > One suggestion I have is for the checkbox "[x] Encrypt backup files" > -- it's unclear whether its only transferred to the cloud encrypted, > or if it's actually stored on the cloud encrypted too. > > For me, I wondered if it meant the difference like using scp vs. ftp > -- once the file is in its destination it isn't encrypted (unless the > file itself is encrypted by some other means)...or whether it actually > stores your data on the S3 server in an encrypted format (obviously > this would be ideal and would be nice to know that if it is or isn't > the case). > > Perhaps: > > [x] Encrypt backup files > (encrypts data on server and while transferring) > > [x] Encrypt backup files > (encrypts data while transferring only) > > > ...whatever the case may be. > > -- > Anthony Ettinger > http://anthony.ettinger.name > [email protected] > +1 (831) 406-1123 > -- Anthony Ettinger http://anthony.ettinger.name [email protected] +1 (831) 406-1123 _______________________________________________ usability mailing list [email protected] http://mail.gnome.org/mailman/listinfo/usability
