News for hackers. Stuff that matters.
Re:Security Flaws in Adobe Acrobat Reader Allow Gaining Root... by toasterlovin on Thursday May 14, 2020 @03:56PM (#23184548)
Open Creative Cloud app. Click Preferences, then Syncing. Folder Location = “/Users/toasterlovin”. That, to me, indicates that it will try and sync that folder.
Re:Security Flaws in Adobe Acrobat Reader Allow Gaining Root... by killerdhmo on Thursday May 14, 2020 @04:15PM (#23184802)
Ah, no. I see your point, this is as a fellow poster indicated, the location for your Creative Cloud Files folder. I will check with the team to see if we can make the language clearer.
Re:Security Flaws in Adobe Acrobat Reader Allow Gaining Root... by hesk on Thursday May 14, 2020 @09:03PM (#23187689)
Thanks for being so responsive. This is a truly alarming UI.

While you're at it, please ask the user whether he wants to sync at all during installation. By default it should not sync.

I only have Creative Cloud installed because I am a Lightroom and Photoshop user. I use the sync feature in Lightroom but do not need another generic file system cloud sync.

Re:Security Flaws in Adobe Acrobat Reader Allow Gaining Root... by derefr on Thursday May 14, 2020 @04:16PM (#23184809)
"Folder Location" = "location where a folder will go." Like when choosing where to unzip something, or where to create a new library bundle in Photos/Music.
Re:Security Flaws in Adobe Acrobat Reader Allow Gaining Root... by toasterlovin on Thursday May 14, 2020 @04:29PM (#23184961)
I get that now. But it’s trying to sync a folder, so why not just point to the folder it’s syncing?
Re:Security Flaws in Adobe Acrobat Reader Allow Gaining Root... by JadeNB on Thursday May 14, 2020 @04:40PM (#23185115)
Because, like every other sync solution out there, though for what reason I don't know, it fears the consequences if you are allowed to name the sync folder yourself.
Re:Security Flaws in Adobe Acrobat Reader Allow Gaining Root... by Reelin on Thursday May 14, 2020 @04:52PM (#23185264)
Not perfectly analogous to specifying folder names yourself, but the infamous Steam deletion bug comes to mind. (https://github.com/valvesoftware/steam-for-linux/issues/3671) Caused by a failure to use readlink (plus not sanity checking variable contents), so introducing a symlink would break it.