4. I confirmed with Adobe that if my computer is log onto the internet I must log into CC to use these CC products.
This is scary, if true. This potentially cripples one's organization if internet connection is disrupted (and these things always happen with a deadline in sight). A cable being torn up by a local contractor, a power outage, even a DDOS attack addressed at the 'right' address would shut down large numbers of people who's livelihood may depend on it. Such vulnerability should not be part of any process/design, without providing alternatives.
6. It is unthinkable to allow a software vendor to delete version releases from ones own computer. Large production shops must have a different agreement with Adobe for product upgrades.
Again, if true, unacceptable.
7. I do not question the intent of Adobe with their required CC log-in. I was informed they need this to fight piracy, but pretend for a moment that Adobe was our Federal Government and every-time you opened your computer you had to log into their system. Would that be acceptable?
The piracy argument is bogus, CC is only about locking people in for more money than it would have cost them otherwise. But I understand why they want to lead people into believing the anti-piracy angle. I remember the day that the new CC was launched, a number of cracks were already available.
BTW, people who use an illegal version, are not the same people who would have bought/subscribed anyway, so no revenue is lost. In fact, these people may promote the product so someone else may indeed purchase a licence, and that's a revenue increase.
I think the security issue is one of weighing one's risk versus the benefits. For non-pros there is little risk and the access is a benefit. For Pros the risks are potentially catastrophic, the benefits are then of no importance at such a time. It would be wise to create a plan-B scenario if one relies on a single solution too much.
Cheers,
Bart
