Google Drive? Oh, well, welcome to sharing your life with Google. Drop Box: *You own your data*: *By using our Services you provide us with information, files, and folders that you submit to Dropbox (together, “your stuff”). **You retain full ownership to your stuff. We don’t claim any ownership to any of it.** These Terms do not grant us any rights to your stuff or intellectual property except for the limited rights that are needed to run the Services, as explained below.* https://www.dropbox.com/dmca#terms
Google Drive: *They own your data*: *When you upload or otherwise submit content to our Services, **you give Google (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works** (such as those resulting from translations, adaptations or other changes we make so that your content works better with our Services), communicate, publish, publicly perform, publicly display and distribute such content.* http://www.google.com/intl/en/policies/terms/#toc-content On Tue, May 7, 2013 at 10:30 AM, David Connors <[email protected]> wrote: > On Tue, May 7, 2013 at 10:26 AM, Ken Schaefer <[email protected]>wrote: > >> Similar issues exist around EFS (since it uses DPAPI as well)* *IIRC >> One way to get around it is to use machine based (or at least pre-user >> auth) VPN technology. Don’t think Microsoft offers this much (except maybe >> Direct Access), but the 3rd party VPN suppliers do. Then your machine >> has connectivity to your DCs before you do a password change. >> > > Crazy isn't it? I have been ignoring the issue for a year but was finally > confronted by Google Drive. When it can't access its oauth secrets it juts > chucks its toys out of the pram and asks you to disconnect and reconnect > your account (English translation: Delete everything from your PC and > download all of your files again). > > Moving my family stuff to the cloud as been ... quite an experience. > Internode are making good money out of me with data blocks. > > David. > >
