Paperback 1.

10 Encoding Tech

State Sponsored Attack @ AES Coding Stage?

Programs almost never ever fail during
crypto encoding, as all crypto code is
highly vetted for correct statefulness
and relyability.

A program that works in one OS

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

Paperback 1.10 fine in Win 7 & 8

without crashing and burning.

Paperback has never ever

totally failed during crypto.
The crypto program failure even
persists in VM modes : AKA
Win 7 & 8 Compatibility Modes.
The same feature worked under
Win 10 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
cryptography crash problem.

NOT USING CRYPTO is

about the only fix, the
program does not crash in
encoding 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
overall 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,
SorceFoge etc) & functionally
updated an upgraded.

Paperback should be
convereted to Java for PCs
and Dalvik for mobiles.
Flaw : Paperback needs to
save to GIF (and Animated
GIF), with up to 40 pages
bandwith.
Paperback needs to support
127 Gray Levels for mobile
file backup.

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)
to create the 2 or 3 separate
Paperback code branches
necessary to keep this encoding
scheme working well into the
future.

Paperback 1.10 Encoding Tech

State Sponsored Attack @ AES Coding Stage?

Paperback is in need of being more publicly opensouced at a
place like GitHub, SorceFoge etc & functionally updated an
upgraded.

Long term : Paperback should be convereted to Java for PCs

and Dalvik for mobiles. C++ to Java transistion can be done.
Bug (1, 1.1) : The last encoded page is never in the format of
the 1st page (and all subsiquent pages) and this makes
encoding the images into an Animated GIF nearly impossible.
Flaw (1.1) : Paperback needs to save to GIF (and Animated
GIF) to save diskspace. Animated GIFs are preferred for
mulipage encoding.
Flaw : Paperback needs to support 256 & 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.

Paperback 1.10 Encoding Tech

State Sponsored Attack @ AES Coding Stage?

Copyright & Copyleft Addendum
Version 03 NOV 2015 bb
Permissible

Mass Exact Duplication.

Attribution.

Branch Variation if 50% new content added.

Public Domain Use (GPL).