21–30 of 186 posts
The real information would be what version of PS this was implemented in (my guess is CC) and to make sure you have the version right before it. :)
This page confirms it was add in Photoshop CS (October 2003): https://gist.github.com/msikma/04bfae8670300a12c55937c3b61d6...
The real information would be what version of PS this was implemented in (my guess is CC) and to make sure you have the version right before it. :)
If I remember correctly, this feature was present when took a graphics art class using CS4 or CS5. Edit: looks like the first CS. https://m.slashdot.org/story/42050
More proprietary software treating their users like criminals as the default.
What legitimate use case can you think of where the benefit of faithfully reproducing currency is not outweighed by the need to prevent the proliferation of counterfeit currency?
More proprietary software treating their users like criminals as the default.
What legitimate use case can you think of where the benefit of faithfully reproducing currency is not outweighed by the need to prevent the proliferation of counterfeit currency?
You cannot make counterfeit currency with Photoshop. Paper money has security features that won't even convert to pixels in the first place, like holograms, transparencies and fibers embedded in the paper and such, never mind reproduce by conventional printing.
This whole deterrence system is idiotic.
People who accept an obviously fake printed copy of a banknote basically deserve it; it goes with their collection of wooden nickels.
A few years ago I extracted the CDS logic and got it working in Linux so I could experiment with it: https://twitter.com/taviso/status/902997594460135424 I had planned to see if I could come up with an image that would still be detected even with significant distortion, and then print it on a t-shirt... The idea being you couldn't open a photograph of me in PhotoShop! :) I got sidetracked, but I should get back to th…
My original goal was to wear it for official documentation, but that went less well. It was cut off in my drivers license photo, and I forget why, but I never ended up wearing it for passport photos.
The real information would be what version of PS this was implemented in (my guess is CC) and to make sure you have the version right before it. :)
The logic is local. Could patch it out in 30 minutes if they dont have any anti circumventions
Earlier quoted context omitted.
The logic is local. Could patch it out in 30 minutes if they dont have any anti circumventions
The first x64 patch I ever did was to remove this very protection from Photoshop years ago. It was a single instruction patch, 1-3 bytes changed, I don't remember exactly.
Earlier quoted context omitted.
The first x64 patch I ever did was to remove this very protection from Photoshop years ago. It was a single instruction patch, 1-3 bytes changed, I don't remember exactly.
Curious, as I'm totally oblivious to this - how does one patch a closed source binary to get around this protection?
For this particular example, Photoshop, an error message is displayed for currency detection. The first thing I would do is load up the executable and look for that particular string. If I'm lucky and there aren't many protections for the executable, I'll be in the right area for figuring out what to patch, or I'll at least know which code paths to start tracing.