Luckily for Adobe, there's that license agreement that dismisses them of any and all liability for their product, and the user agrees that all risk is on themselves. Standard in this industry.
wonderful industry we got there. Wonderfully unethical.
So, what would be the benefit of this functionality? Why would Adobe want to erase contents in a random root folder? Does this feel like malicious code to anyone? And how likely is it that no one would catch it unless it was hiding or waiting to function? Not a coder, just asking...
So, what would be the benefit of this functionality? Why would Adobe want to erase contents in a root file? Does this feel like malicious code to anyone? And how likely is it that no one would catch it unless it was hiding or waiting to function? Not a coder, just asking...
An 85er here. It's funny that many of you are as old or a bit older than my father and, yet, I am pretty much on the same page as you all. I keep everything on two backups, an always plugged in LaCie Quadra configured with Time Machine and a bootable, bare hard drive which I periodically plug into a USB dock to update with CCC and otherwise keep safely stowed away at a relative's place.
For my most recent stuff, especially ongoing work which may not be backed up on my secondary CCC backup, I have a few different cloud services; iCloud for Apple and iOS apps, OneDrive for Office files (for my academic work, which is mostly made up of Word documents and the odd PowerPoint presentation), and Dropbox + Google Drive for colleagues and clients, depending on their personal preference.
That way, since I usually update my CCC backup whenever I purge photos and movies from my iPhone or finished projects to make way for new ones, if my house burns or if it's burglarized I can get up to speed with my CCC and cloud backups in no time and lose only a negligible amount of data (random stuff on my Desktop and app preferences, mostly, since iCloud already syncs a lot of stuff by default).
Fixed an issue in the Creative Cloud for desktop app for Mac where in some scenarios the application may incorrectly remove files with user writeable permissions from the system root directory.
Fixed an issue in the Creative Cloud for desktop app for Mac where in some scenarios the application may incorrectly remove files with user writeable permissions from the system root directory.
If you're going to force your customers down the subscription route, the least you can do is not screw up their systems.
Not quite sure why user level software have such wide access anyway? Though of course, deleting from the user level root is only relatively better (at least you probably have a chance at recovery if this happens).
I've been affected by this bug and have two questions: 1.) How do I log out of Creative Cloud (be specific). 2.) How will I know when the problem has been resolved so I can safely log back into Creative Cloud?
I gave up on Adobe several years ago after being screwed out of free upgrades one time too many. They began as great company and evolved into one with little or no commitment to their customers. Of course their quality reputation long since went by the wayside with their lousy Flash product. Moving to the subscription model was another bilk-the-customer move. I'm happy to say I no longer use anything from Adobe and am better off for it.
Fixed an issue in the Creative Cloud for desktop app for Mac where in some scenarios the application may incorrectly remove files with user writeable permissions from the system root directory."
So, what would be the benefit of this functionality? Why would Adobe want to erase contents in a root file? Does this feel like malicious code to anyone? And how likely is it that no one would catch it unless it was hiding or waiting to function? Not a coder, just asking...
I imagine they were trying to remove temporary files they dumped on the machine during installation, and poor coding/testing led to other files being caught in the sweep.
Really glad I never upgraded to Adobe Costly Cloud.
Now Apple needs to be called to answer why Adobe, or any other app developer, has the power to do this.
Because if Apple stopped users/developers from doing this then Macs would stop being the machine favoured by a huge chunk of the developer community.
Secondly, Apple didn't give developers the power to do this – you did. Each time Adobe runs its malware installer it asks for permission to dump its crap all over your machine. And everyone always says 'yes'.
There's not much Apple can do about this except lock the machine down to the same extent they lock down iOS, and how well do you think that would go down?
This is the dawning of the age of idiocracy, the age of idocracy. The spawn of the babyboomers are in positions of responsibility, and guess who didn't get any life lessons in personal responsibility. It'll only take another generation for them to starting putting Brawndo on our crops, sowing the seeds of humanity's demise.
Don't blame us B-B's. Most of them have retired already. Blame the new kids on the block (complete with MBA's) who are addicted to being online all the time and that all your data belongs to the supplier especially if you were foolish enough to put your stuff in their cloud. As a soon to retire B-B (born 1953) I refuse to put anything of value in a cloud. When it rains, the clouds go away. none of my peers are cloud fans. You might think that we are Luddites but we value our privacy. Having written my first program in 1972 (puched cards ICL Mainframe), I've been there, done that , got the Bite marks to prove it.
Born in 51. I have Time Machine back ups that go back to 2009. So if you need any critical files for Leopard I might be able to help.
Really glad I never upgraded to Adobe Costly Cloud.
Now Apple needs to be called to answer why Adobe, or any other app developer, has the power to do this.
Because if Apple stopped users/developers from doing this then Macs would stop being the machine favoured by a huge chunk of the developer community.
Secondly, Apple didn't give developers the power to do this – you did. Each time Adobe runs its malware installer it asks for permission to dump its crap all over your machine. And everyone always says 'yes'.
There's not much Apple can do about this except lock the machine down to the same extent they lock down iOS, and how well do you think that would go down?
Considering IOS dev is going swell, I think it would go all right. They'd just have to adjust the way they do things a bit.
I think they do have to lock down apps tighter; giving admin right, or non granular rights (which is something a lot of windows apps ask on install) is one way to disaster and very bad for security.
Doesn't mean you have to lose access to a file system, you just give the apps access to a "view" of the machine (but a wider access to resources than virtualization).
Comments
wonderful industry we got there. Wonderfully unethical.
For my most recent stuff, especially ongoing work which may not be backed up on my secondary CCC backup, I have a few different cloud services; iCloud for Apple and iOS apps, OneDrive for Office files (for my academic work, which is mostly made up of Word documents and the odd PowerPoint presentation), and Dropbox + Google Drive for colleagues and clients, depending on their personal preference.
That way, since I usually update my CCC backup whenever I purge photos and movies from my iPhone or finished projects to make way for new ones, if my house burns or if it's burglarized I can get up to speed with my CCC and cloud backups in no time and lose only a negligible amount of data (random stuff on my Desktop and app preferences, mostly, since iCloud already syncs a lot of stuff by default).
If you're going to force your customers down the subscription route, the least you can do is not screw up their systems.
Version 3.5.1.209 released on 2/14/2016
Now Apple needs to be called to answer why Adobe, or any other app developer, has the power to do this.
Though of course, deleting from the user level root is only relatively better (at least you probably have a chance at recovery if this happens).
1.) How do I log out of Creative Cloud (be specific).
2.) How will I know when the problem has been resolved so I can safely log back into Creative Cloud?
No sensitive info of mine goes in any cloud, it's too visible to others and can be lost by a disappearing cloud.
Adobe posted an update to CC today:
"Version 3.5.1.209 released on 2/14/2016
Secondly, Apple didn't give developers the power to do this – you did. Each time Adobe runs its malware installer it asks for permission to dump its crap all over your machine. And everyone always says 'yes'.
There's not much Apple can do about this except lock the machine down to the same extent they lock down iOS, and how well do you think that would go down?
I think they do have to lock down apps tighter; giving admin right, or non granular rights (which is something a lot of windows apps ask on install) is one way to disaster and very bad for security.
Doesn't mean you have to lose access to a file system, you just give the apps access to a "view" of the machine (but a wider access to resources than virtualization).