Paperback 1.

10 Encoding Tech

State Sponsored Attack @ AES Coding Stage?

Programs almost never ever fail
during crypto, as crypto code is
highly vetted for relyability.

A program that works in one

OS will generally work
identically with its "child or
grandchild" OS.
Some crypto code can be too
efficient (but not here)!
NB : SSL/TLS commonly has
randomly imposed
wait(rnd_x_ms) to work
around "CPU time"
fingerprinting attacks.

Paperback works without flaw in

Win 7 (and Win 8) without crashing
and burning.

Paperback has never ever

busted during crypto.
The crypto program failure even
persists in VM modes, Win 7 &
8 shell for compatibility.
The same feature worked under
Win 10 with the patches it had
as of OCT 2015 so somting is
up
C++ code is of no help in doing
the diagnostic research!

Paperback 1.10 Encoding Tech

State Sponsored Attack @ AES Coding Stage?

Windows 10 Only...

Paperback 1.10 Encoding Tech

State Sponsored Attack @ AES Coding Stage?

Refreshing the Paperback
binaries from the website and
archived copies does not fix the
problem.

NOT USING CRYPTO is

about the only fix, the
program does not crash in
plaintext mode.
It is really impossible to find
any other explaination
besides a 'state sponsored
attack' to explain the crash
and burn in AES encoding
mode.

Paperback's crypto is not worth

attacking: it is only a single step,
single key system -- more for
data integrity than deep security.

Paperback's crypto encoding

schemes are universally
overblown : without 2 stages,
2 algorythems & 2 keys there
is no cryptography security.
Even in the clear the
encoding density of
Paperback is somewhat too
low to be of deep stratigic or
operational value.

Paperback 1.10 Encoding Tech

State Sponsored Attack @ AES Coding Stage?

Paperback is in need of being
opensouced (@ GitHub, SF etc)
-- and in general functionally
updated an upgraded.

Paperback should be
convereted to Java for PCs
and Dalvik for mobiles.

The author of the research does

not have the time, energy of
facilities to create a branch of
the Paperback code -- and give
it the new life and funcitionality it
deserves.

It will have to be up to someone

else (or several dozen people)
Paperback needs to save to
to create the 2 or 3 separate
GIF (and Animated GIF), with
Paperback code branches
up to 40 pages bandwith.
necessary to keep this encoding
Paperback needs to support scheme working well into the
future.
127 Gray Levels for mobile
file backup.

Moral : C++ code is dangerous...

So, Minix3 etc ... should be rewritten in ADA95.

Java is avalable for this transision as well.
Most of the C++ code in the wild has all sorts of problems, and the expence
of maintaining it in Open Souce systems is still higher that what society can
afford.
Closed Source C++ code has bankrupted nearly every company that ever
used it, and there are no signs of improvement. Microsoft probably had to
auction off access to parts of Win10 to GCHQ, NSA etc ... just to have the
spare cash to allow it to unifiy its massive horde of accumulated C++ code.
Minix3, The NTP Server, etc ... all need to be rewritten in ADA95 (or for nonembeddedable use ADA14) for safety and maintainability reasons.
For a lot of C++ code, there is the option of a transistion to Java a
language with most of ADA's safety features (but a syntax closer to C++).
The EU should take measures to halt the further use of C++ in the
Euroshpere to reduce the safety of life issues associated with its use.