| Very good post. Maybe you should crosspost to
| alt.comp.freeware.
|
Thank you. I've never used that group. Maybe I'll
check into it. Though I'm ambivalent about supporting
people with a "free or bust" attitude. :)
| Wondering what you compiled SumatraPDF with. Site says "You'll
| need Visual Studio 2012". I did not realize that DRM could be
| switched off, I thought it was in some micro$oft library the program
| used, and one of the reasons I was using other PDF-readers. Maybe I'll
| just Ollydbg Sumatra. Write a binary patch if the code is +-
| consistent through versions.
|
I'm a bit behind with versions. My last version
was 2.1.1. The current version is 2.4. I think I
used VC 2008 Express. The new version may
require VC 2012. In the past the Express versions
have been free, though I can't say for sure that
VC 2012 is free.
The restrictions in PDFs are not DRM. They're
just flags, presumably stored in the header. It's
really just a clever scam instituted by Adobe to
make PDFs seem as "concrete" and immutable as
printed pages, which is something business people
very much want to think is feasible. Thus, a format
that's not good for much of anything other than
accurate printing has become the default for
anything official in business or gov't.
The only reason PDF locking works is because people
writing PDF readers respect the flags, and unlike, say,
HTML or DOC files, PDF is extremely complex. So if the
people writing the software respect the flags then
the format is lockable for all practical purposes. But one
need only ignore the flags, editing the source code to
bypass the flag checks. And in doing so one is not
bypassing any DRM or reverse engineering anything.
(Nevertheless, I don't distribute my Sumatra version.
I figure it's not for me to override the authors wishes.)
Unfortunately, in many cases the restriction flags
are set for no reason: Authors who don't know what
they're doing; gov't documents locked for no reason
other than frivolous, overzealous officiality; etc. Which
can be quite a pain. To copy text from a PDF like that
usually requires a screencapture sent to OCR software,
followed by some editing of the result.
| I also do not trust AVs anymore, specially the cloud-enabled
| types, but I do recommend them for the clueless.
|
Yes, it's hard to argue with having AV if people don't
want to keep track themselves. Anyone who wants
Facebook, webmail, or anything else that requires
allowing script and/or Flash indiscriminately, has no way
to be reasonably secure online.
But it's a shame. In my experience AV programs have become
extreme resource hogs, comparing byte streams to 10's of
thousands of "virus definitions"
every time a file is touched, and updating several times
daily. It's become an untenable approach. Many attacks
are using zero-day exploits, anyway. There have even been
articles about a market in zero-day exploits, with the NSA
apparently even more involved in criminal hacking than
Russian mobsters:
http://www.tomdispatch.com/blog/175803/
AV is mostly useless for that kind of thing.
| You forgot Nirsoft, and a text-editor (Notepad++), both
| essential, IMHO.
| And CPU_id (CPU-Z) and Imgburn both phone home (check your
| logs)
It is getting hard to find truly clean software. Some
of it's well intentioned. But even with those, I don't know
how the idea became popularly regarded as reasonable
that all software should be placed on an update drip-feed;
programs being changed willy nilly, without notice. It's
not a stable approach.
If I remember correctly, ImgBurn shows a message at
first start allowing updates to be disabled. I never had to
block it. But I do have cpuz.exe blocked. I'm using a
firewall that blocks unauthorized outgoing. I usually
also unplug the network cable when installing anything.
Some installers will hang if they detect a network connection
but are blocked from getting through.
Even the Mozilla products and extensions have an annoying
habit of trying to track installs by sending the browser to
their homepage on first run after an install or update.
| Maybe we could start an about:config thread back in
| alt.comp.freeware. To make Firefox freeware again. IE and Chrome are
| built as malware, there is nothing that can be done to avoid the
| spyware.
There is a lot that can be done. Last week I discovered that
I could replace the normal download window in FF 23. By
downloading the relevant .xpi and examining the code one can
make the pref changes and avoid installing more extensions.
And some extensions can replace the missing settings in the
Options window.
But it seems to be a losing battle. Those solutions are only
feasible for a very few people, and even then they're limited.
According to what I read, the download window is removed
altogether from FF 26! They break a function pointlessly one
month. The next month someone writes an XPI fix. A month
after that the Mozilla people break it permanently! The only
decent solution I have at this point is simply not to upgrade.