P: Photoshop 23.0 - cannot open TIF files, generated in other programs

@Verto 

I have indeed read the comments through this thread and others, and am also a user affected by the issue. I am not an employee of Adobe just a user who also works daily with Photoshop in a workflow with several other applications. I am sure that, given Jeffrey's comments, if there is a secure way around this issue it will be implemented. Whether that resolution is a big or small problem to implement, neither of us know as we are not Adobe developers.

We should though be directing some of these comments to the owners of those applications that are outputing non-compliant TIFFs, not just to Adobe who are closing the security loophole.

Can you please confirm if SNS-HDR tiffs will open with 22.5.2?  I have 22.5.1, and 23 doesn't work for me with SNS-HDR tiffs, and I'm worried about updating to 22.5.2, and whether it will not work and prevent me from reverting back to 22.5.1.  But 22.5.1 has some strange bugs that causes very long spinning wheel.

Let's not pretend that Abobe suddenly became so security conscious after years of flash problems. Look up the CISA database and they are late fixing things. It's convenient that challenging security headers from Capture One and other third parties suddenly matters. It is on Adobe to provide correct APIs and proposed changes to the companies that use them in a timely manner so they can be accomodated without springing it on everybody with an upgrade to PS 2021 and 2022 so user workflows and businesses are impacted. Hiding it all under some nebulous "security change" doesn't cut it.

"Did you read the security info linked earlier in this thread?..."

Yes Dave, I believe I have read the entire thread, and I am aware of the answers given and the reasons given by Adobe for implementing this security measure.

However, I do not consider it a big problem to add an option in the Photoshop preferences settings, so that the user can decide to enable or disable such a measure, while other manufacturers are implementing security in their applications.

What cannot be done is to make an unequivocal decision, which implies the loss of time and possibly money for users. Some of us work daily with Photoshop and other image processing programs, and this measure is creating a serious problem for us, given the enormous amount of TIFF files we handle. And considering that Photoshop is a paid software, we would like to receive a good service.

I hope that in addition to reading Jeff Tranberry's, whom I thank for his attention and response, you will also read the comments and responses of the affected users, and put yourself in their shoes to understand them.

Thank you for your attention and best regards.

".....but if Adobe now, in order to protect its own application ecosystem............"

Did you read the security info linked earlier in this thread? Adobe are not doing this to protect their ecosystem. They are doing it to protect vulnerabilities exposed on your system which potentially open up your system and data to attack. Read the links carefully.

I have no doubt Capture One is producing legitimate files. I am also in no doubt that the vulnerabilities in the TIFF files can be used by unscrupulous parties to attack your system. The recipient of the file in this case Adobe Photoshop, can only act to shut down the vulnerability. If Adobe knew about it and did not act then that is irresponsible and we would quickly be shouting about lost data. 

Adobe have already stated that they are looking for a way to make these files open without that exposure - see Jeff Tranberry's response.

Dave

I have problems with TIFF files created with Capture One. Photoshop forces me to open them through Camera Raw.

We are told that the problem arises from a security measure, to prevent malware, but I don't believe that software like C1, is introducing malware into the files. That software is an industry standard for taking and processing RAW files, just as Photoshop is a standard for image editing.

The full compatibility between the two platforms guarantees both manufacturers many customers, but if Adobe now, in order to protect its own application ecosystem, hampers C1-generated files, I fear it will unfortunately lose customers, as Lightroom is still behind C1 in many respects.

Many professionals who have invested in purchasing C1 licenses, were not going to switch to Lightroom now. For most jobs, it is easier for us to switch to programs like Affinity Photo as an alternative to Photoshop, if we can maintain a streamlined workflow.

I'm sorry but this is Adobe's problem to sort out, that is one of the reasons we pay a subscription. I can't believe it is that difficult, after all two of the workarounds include using other Adobe products, Bridge and Lightroom and it's not causing an issue there it would is seem. 

Photoshop seems to be only one protector of users while there are still plenty of other apps handling the tiffs the old way. The hint is to temporarily let these files be treated like so far (with option to disable), even assign official date of permanent disablement, at least as the signal to other brands to reconsider the same. Whatever direction would they take, at least the preparation time for the users to any scenario would be given.

How many people would just click through and get pwned? Everyone posting in this thread... this is why we have so much malware.

You may start a request thread basing on 'Nov, 05 2021' post argument.