bk AHC: How complex code is good enough? (10)

An excerpt from the book Advanced Handwriting Cryptography..

full book sellfy.com/p/ujMc / free examples sellfy.com/p/HQH3

__

[ i have skipped (not posted on the YE blog) the chapters 7, 8 and 9 of the book. you must get the full book to read them (check out the CONTENT of the book). perhaps i will also skip the chapters with code examples, because these are available on the free version of the book. ]

/…/

Perhaps you have realized how strong can be the encryption method, how difficult it will be to crack the code even if you are a bit careless during encryption. It must be made so strong as principle because as humans we make mistakes which weaken the code. So if theoretically it is impossible to crack the more advanced versions of the code, and even if someone will have access to all of your encrypted writings, including diaries with encrypted private entries, then all the cumulative unwilling giveaways of context of the cipher text and a bit careless encoding in some places should leave the script still impossible to crack. You may think that creating a simple code is good enough for your needs, without paying much attention to all kind of tricks to make it a well secured advanced code. But think about it how often you would actually want to use your method: only occasionally (codes), for one thing only (a diary), or you want to be able to use your encryption method at any time during entire life, whenever needed? Sometimes we can make really bad mistakes in life, so it may happen that you do leave around a plaintext of some notes together with the encrypted text. If your encoding method is too simple then one such mistake will compromise all your encrypted data in the past, and if not noticed then all your future encryptions as well. Is it really worth spending the time then to create your personal method? Perhaps it will be safer to rely on your memory alone than on a weak encryption, in case of passwords and other such type of data. Taking the time to learn the art of handwriting cryptography well, with all the precautions and tricks, is a good investment to avoid any trouble in the future. If you create your own method which have not just a single pattern of encoding but at least a hundred ways of representation of the same symbol or word (which is still a relatively simple code) you may feel quite safe that someone having access to the plaintext data together with the cipher text will not derive by it the rest of your private information.

/…/

Advertisements

bk AHC: Basic principles of handwriting encryption. (6)

An excerpt from the book Advanced Handwriting Cryptography..

full book sellfy.com/p/ujMc / free examples sellfy.com/p/HQH3

The following principles or rules are not necessarily in the order of priority — all of them are important. I’m numbering the rules just for easy following and in the order they come to my mind.

Rule 1:

Never keep plaintext and encrypted text together. Never show off anyone how beautiful is the encryption method representing your name or else. If it’s unavoidable for whatever social reasons then show it generally writing down a wrong thing in a wrong way.. and if asked much later what does it means then simply say you probably made a mistake and can’t understand.

I can imagine that after creating a personal code the excitement of the achievement may trigger the emotions to show it someone, but it may cost you lost privacy and/or extra work to create a new code. You may only show the exact encrypted writing to someone you’re planning to share the particular code with.

Rule 2:

You should always encrypt as little text as reasonably possible, encrypting only the parts which need to be encrypted, the related parts of text which would give out the information about context of the encrypted text, possible sources of the encrypted text and other content having references to the encrypted text.

The less data you encrypt and fewer references you leave about the encrypted text the less vulnerable it will be for attacks by cryptanalysis. When encrypting whole the context is impractical then don’t insert the encrypted part directly into plaintext — instead insert an encrypted reference to the place where you hold the actual encrypted part belonging to the document.

Rule 3:

Never write a script without including at least a minimum amount of information noise — the symbols and extensions which actually mean nothing. Write into a cipher text about 1/5…1/10…1/15 of symbols as a noise and varying the amount of the noise from place to place.

Using the noise level and quality of it properly makes exponentially harder to crack the code by cryptanalysis while still keeping the script easy to read without affecting the process of decryption.

Rule 4:

Never write down text, specific names and codes in the same script using the same encryption method/pattern or set of symbols.

Having an accidental access to one of them will make it easier to crack the other part of the script if encoded with the same method and/or set of symbols. It doesn’t mean you will always need to write down different data with completely different encryption methods, you need at least to use different keys of encryption within the same method.

Rule 5:

Create a simplified public set of symbols to write down stuff temporarily but fast and still quite securely while others are watching and may guess the content.

Later you can rewrite the data in another place with private and highly secure code while destroying the public version of the same script.

Rule 6:

Never correct encryption errors by writing a correct symbol above the wrong one. Include in your encoding method hidden (also encrypted) tools for backward deletion, insertion, replacement and other correction symbols, and special signs indicating errors if placed in the right position but otherwise used as noise. If an error isn’t important leave the error uncorrected. If not possible to leave an error in and to correct it then write the data again correctly with other symbols leaving the error untouched. If none of the above works for you then destroy the wrong symbols leaving no traces of them before writing correct versions above.. or destroy whole the script and write again.

Indicating your errors is a good help for cryptanalysts, leaving the errors into the script is the cryptanalysts’ nightmare.

Rule 7:

Never use classical grammatical signs within encrypted script. All the signs like periods, commas, apostrophes, dashes and any other signs, also real positions of spaces, line breaks and other grammatical rules must be encrypted and hidden within encryption. An encryption must give no hint whatsoever what it is about. Don’t even use any classical signs in wrong places as a noise — use only random false spacing for breaking and combining ‘words’ into the blocks with not the real length.

Placing classical signs within encrypted script is an excellent help for cryptanalysts to guess the content. In some cases you may use the classical signs as a noise (in wrong places), to confuse others, but if you’re not careful enough you may give away some information unwillingly just because of your habits (dropping accidentally the signs into right locations).

Rule 8:

Never highlight any part of the encrypted script in classical style for easy following. For highlighting use encryption rules you could easily spot if necessary but which wouldn’t look special to others.

Highlighting parts of the encrypted text, like underlined or bold script, is an excellent help for cryptanalysts to guess the content. If you do need to include highlights for the text you’re encrypting then you must create corresponding, visually hidden rules and code symbols for use within the encryption, including code representations for colors, size, font, background, etc.

Rule 9:

Never use within encryption the actual length of encrypted words and even sentences to make it look better and easier to read.

Writing encrypted script with the actual length of encrypted words is the best help for cryptanalysts to guess the content and will greatly diminish the strength of encryption. In some cases, writing long pieces of text, it will render the use of almost all the other precaution rules practically pointless — by the frequency of words and the rules of grammar in a language a computer program will easily be able to make sense of your encrypted text.

Rule 10:

Never back up any part of your personal encryption method in a computer during or after creation of it  all keys must be destroyed. You must rely on help of paper notes during development of your method and on your memory alone. You should never leave around any traces of the keys and the systematization used in your encoding method.

That’s an obvious one you may guess, but there are still people out there thinking they can trust their computers – do not, that I can assure you. If you do need to write something down for visualization, before you learn to do it in your mind, then you must destroy the paper each time you stop working on the code. To work on the code the next time you will write it all down from memory and will continue (that’s an excellent training by the way). You can storage ready scripts (cipher texts) in computer with no worries, but never together with the plaintext related to the script as it may significantly weaken your code making it vulnerable for further attacks.

Rule 11:

Create your cryptic symbols different from any known to you symbols (not borrowed from any language), with several layers where the separate parts are difficult to distinguish and not easily understood by others, so that they’re not possible to input into a computer program automatically.

Your cryptic symbols must be complex enough requiring human work on each symbol trying to take it apart. If you create single layer symbols, with each corresponding to one actual symbol, then a scanned document can easily be translated into a computer language and a program can figure out the actual symbols by the frequency analysis.. and to crack the code in no time.

Rule 12:

Always test your every newly created encryption method with a reasonable amount of cipher text, storing some complex, difficult to remember data which you can verify later. After you have forgotten the complex data sets, successfully deciphered the code and verified against errors, only then you can begin encrypting important data which you can’t afford to lose.

The length of the cipher text for trial depends on the complexity of the code — it should include all of the essential elements of your code several times, to make sure you won’t be confused yourself while deciphering the test data. The plaintext used for testing must not be kept anywhere together with cipher text or separately — the plaintext for testing must be a part of a larger volume of text/data but the location of the part used for testing must be only for you to know, never highlighted within the volume.

Rule 13:

Read again the first rule of the basic principles of handwriting encryption. If you’re a very social person and like to share things then for social needs you can create a code for fun which you never use for encrypting important data. Your own personal code shall remain the murkiest mystery for others.

Cryptography is fun, and fun is always better when it is shared with others, thus creating a simple code just for fun is a reasonable thing to do.

Continue reading “bk AHC: Basic principles of handwriting encryption. (6)”

bk AHC: The method. (5.3, 5.4)

An excerpt from the book Advanced Handwriting Cryptography..

full book sellfy.com/p/ujMc / free examples sellfy.com/p/HQH3

5.3 Learning all the details.
When you’re familiar with the layout of the book, gone through all of the chapters and ready to begin a proper study, take it with small steps, few chapters at time but not whole the book. Why? Because in a quick study the new information won’t settle in your brain, the necessary connections in your brain cells won’t become strong enough (there will have formed not sufficient amount of supporting connections between your brain cells for the learned information), thus if you learn fast new and again new information, although you can get a quick understanding you’ll forget half of the information the next day. In cryptography, forgetting half of the things is a big deal. Even one thing forgotten may ruin your life’s work if that one thing happens to be of a great importance for the security of the method. Read few smaller chapters at time, and bigger chapters by smaller parts at time. Leave the book for a day or few, and then go through the last studied chapters again, to make sure you haven’t missed anything. You must understand all the important parts of the method by heart, by logic. If you don’t, then seek supportive information in other parts of the book, from previous or later chapters, and then read the chapter again till you get it entirely. And so on, little by little, whole the book, even if it takes several months or a year to study. It’s better to spend a year on learning the method among other things you do in your life, than learning the encryption method fast missing some important information that the book is trying to teach you. That’s one reason why some elements of the method are repeating throughout the book — it’s because they’re important and you should not miss them. There’s also a possibility that I will have not explained something in a necessary detail, because for me all is clear but I’m not inside the mind of a reader. With all the great effort to end up with the best explanation I’m also aware of the possibility of creating a boring read if I should take the readers as not sufficiently intelligent. Thus, in the compromise of creating the book compact and interesting while explaining everything necessary, I have left some elements for your own imagination. In certain parts I point it clearly out — your own creative work is needed for the safety of the code. Thus, there is a possibility that you will read a chapter over and over again but won’t get the point. Although sad then, but in this case just skip the part and read on, relying on your own creativity and logic in the future, to close the gap on the missed part of the book. If in the end something still wasn’t clear then most likely it wasn’t that important, because all the important parts of the encryption technique are explained in great detail in each level, and repeated throughout the book when necessary in the context of specific sections.

5.4 Working on your own.
After your study of the encryption method is properly done and you feel that you’re ready to create your own code, you should try first with simpler methods of encoding. It is obviously depending on the level of understanding you have achieved. I am quite sure that not everyone who reads the book even several times, and thinks that all is clear, is ready to embark in the more complex levels of encoding. The more complex methods require simultaneous interplay of many details, none of which can be created wrong. And you should not put everything down on paper for the safety of the code, which I’m explaining in several parts of the book. That ability to have in mind without any errors the whole picture of the key to the code, even if it is your own code, comes with practice. It’s like with learning to play a musical instrument — little by little your attention to detail during musical handling of an instrument (playing) becomes automatic and you can take up ever more sophisticated tricks, up to the point when it all becomes so easy that you can create a piece of music having it all in your mind completed before even touching the instrument. Don’t try to become a ‘maestro’ of handwriting cryptography from a first try — take it one step at the time, beginning with simpler codes first. After you have successfully created a simple code (with the tools and ways of writing provided in this book, if you like), verified it against errors through practical trials, then you can begin making a layout of your very own original method, a complex one at this point, but still you better practice with the simpler methods as well, created with your own original tools and style of writing. Your perfect complex method will take time to mature, thus playing around with simpler methods provide you with some fun, give you new ideas for including in your advanced method, and also will help you at times in making notes in a secure way before your advanced method is complete. Most importantly, creating a simple code takes less time which is a way to achieve satisfaction from your creative work, to get the feeling that something has been done and is useful. It will be very frustrating to end up with no results if you get right on to the most complex version of encryption and won’t succeed to complete it for a long time. Trust me, you’ll be better off creating simpler codes first even if later you discard them from use.
Your handwriting code is complete when you’re ready to use it for storing data without worries about it being possible to crack nor about losing the data yourself due to confusion in the elements, all the keys of encryption in your mind and no traces of the keys left behind.
In the end of the book (chapter 28) I give you some selected samples of writing in different alphabets, hieroglyphs and shorthand (from Wikipedia and other public sources), used in the past and in use at the present time, for visual help in creation of your own style of cryptic writing. It is very important to detach you from my way of cryptographic writing, to give you some different ideas how writing can be done. But that you will need in the end — before that you shall learn how it’s done in my way of writing.  I will not be surprised if you will find my way of writing of the glyphs the most convenient one, because I’ve been through many different trials with other types of glyphs as well, in the first years of my search, until I found that the current way, presented in the book, is the only way to do it. This way provides security, flexibility, clarity, precision and the result will look beautiful as well.
Here’s an example how you would do without an assistance..

ahc_5.4_a

..actually that’s a specimen of Proto-Sinaitic script, one of the earliest (if not the very first) phonemic scripts. (No copyright on this picture).
Anyway, as you have read the book this far by now, before to continue reading on, with the next chapter waiting, now is the time to pause reading and to get familiar with all the pictures of the cryptic writing in this book. Have fun.

[ the book -> sellfy.com/p/ujMc ]

bk AHC: The method. (5.1, 5.2)

An excerpt from the book Advanced Handwriting Cryptography..

full book sellfy.com/p/ujMc / free examples sellfy.com/p/HQH3

5.1 Getting an idea.
Before continuing with the next chapter, on the basic principles of handwriting cryptography, take a tour through the book looking carefully at all the pictures of the cryptic symbols you’ll find — all the hieroglyphs and all the elements of the glyphs. Don’t try to understand them — you will not. Just look like an artwork paying attention to details and see if you can find similar details in several places of the ‘art’, a kind of characteristic signature of the artist. Try to make sense of the art as pictures, and that’s it in the beginning — you only need to get a general idea what’s going on in these pictures, without guessing what’s the message the artist is trying to convey. Before going through all the pictures of the hieroglyphs don’t read the book yet more than till the end of this chapter, ‘the method’. From curiosity you can peek into the text of some chapters or sections deeper as well, it’s not forbidden of course, but you’ll be better off if you will continue with the next chapter, ‘basic principles of handwriting encryption’, later. The point here is that you will get much better understanding of descriptions, explanations and the terminology used in the following chapters when you have in your mind an overview of the many ways of writing the glyphs.

5.2 Seeking the information.
After you have gone through the book studying the pictures of the hieroglyphs, read the basic principles of handwriting encryption and all the following chapters. Read the book thoroughly till the end, but don’t study everything in detail yet. Learn the general message in the book, to know in which parts of the book you can get an additional information and explanations when needed, when you’ll be studying the method properly on the second read. In the first read of the book you don’t need to understand everything. No need to go back and read again if something isn’t quite clear. But you do need to go through whole the book, the parts which deal with the cryptography method, to have a picture of different sections of the book which deal with specific elements of the method. It is way easier to learn the method later when you have an overview what is where to be found. Some chapters of the book are easier to understand when you have already been through later chapters, with the technique of encoding already understood in general, but without all the details yet. Of course you should try to understand everything you can, even from the first read, but don’t enforce on yourself the condition of not going to the next chapter before all is clear, because some details may just be missing yet for the full comprehension. Or to put it differently — even if you get everything from the first time you will definitely be short of understanding of all the context in details and possibilities of interaction within the cipher text.

[ the book -> sellfy.com/p/ujMc ]

bk AHC: The method. (5)

An excerpt from the book Advanced Handwriting Cryptography..

full book sellfy.com/p/ujMc / free examples sellfy.com/p/HQH3

The handwriting cryptography method which Ive created is one of those methods of encryption which is not entirely affected by just a few errors, and this makes it particularly hard to attack by cryptanalysis because you can leave the errors in, yet being capable to read the text later. For encrypting the data which wouldn’t support any errors (for example codes, telephone numbers) theres possible to write it down several times without repeating itself, in different ways, thus not repeating the encryption error. I have also developed a method for encrypting a single symbol in a manner that it verifies itself against an error of encryption, but this method requires more complex data processing in mind which is not the optimal solution when you want to write up some data fast. Its better to write up something twice in different ways  if one gets wrong then hopefully another one will be right.. in any case it’s easier to recall a code when most of the symbols can be recovered, against the situation when it has completely escaped you what was the login, password or a name of your private business contact. In fact, believe it or not (later I’ll show it), with my latest method of encryption is possible to encode a single letter, number or any other symbol in hundreds of ways with the help of a simple set of extensions to the script, making it the most secure handwriting cryptography method I have created, and yet it is more practical to use than my previous methods as it requires less information to remember. It opened the possibility to learn the method by those who for using securely previous methods would have needed special memory training for remembering all of those hundreds and even thousands of different symbols. Now you can be satisfied with just a handful of rules without the need to memorize too many different hieroglyphs. So far I havent seen any other handwriting code which comes even close to my method by its flexibility in design, simplicity in use and the level of security it provides, all in one package.

Basically, while a single symbol can be written in hundreds of ways then a two letter word can be written in tens of thousands of ways, a three letter word can be written in millions of ways and so on.. can it get any better than that? And you can do the same in your own way, so neither I nor a professional cryptanalyst with the help of an array of most powerful computers can crack your code if you use all the necessary rules and precautions properly. When you customize existing encryption tools and for addition create your own tricks embedded and hidden in your script then no human can ever guess and input all the possible tricks into computer programs for cracking your code.. it all comes down to your imagination in creating your script.

I’m quite confident that a handwriting encryption with your own symbols and rules can give you way much better security than any computer encryption will ever be able to provide, when it comes to encrypting symbols of course — I have yet to come up with an idea how to encrypt pictures in handwriting and I’m not taking on the task any time soon I guess. Computer has a fixed set of symbols and rigid rules of encryption while you can create unlimited set of symbols and rules — only you will know which symbols or parts of a symbol carry information and which are just a meaningless noise.. no computer will ever be able to go through all the possible combinations of human imagination to crack a well created handwriting code.

So, lets get started with studying the advanced handwriting encryption methods which I’m promoting as the best in the world — so far anyway — at the time of working on this book there was no competition of the same level. You can do your learning the way you like, but I will describe you here the way it should work the best for you, in my opinion.  It’s better not to read the book like a mathematical manual in clearly described steps. The book isn’t written that way and thus it is not supposed to be consumed intellectually as a “how to do” manual in classical terms. Because this cryptography method isn’t simply to copy and to use.. you must get the big picture of the possibilities of the encryption technique and then create your own code with your own cryptic symbols and your own other keys of encryption (the matrix of real symbols and the rules of access of the real symbols). Thus, take the book as a book of art.. read it, look it, get an idea, and then read it again and again, each time with a better insight to the method and better set of tools in your mind, picking up things you missed before.

bk AHC: Relevance.

An excerpt from the book Advanced Handwriting Cryptography..
full book sellfy.com/p/ujMc / free examples sellfy.com/p/HQH3

I could simply give the principles of the latest encryption method, to explain the basics and the ways to personalize the code, but in that case you may not be aware of the precautions of use. It could be possible to explain the method in an hour to someone used to intellectual exercises, to regular challenges of the brain and to applying logic with common sense in daily life. But, there may be important points which are better to explain in detail right in the beginning, not letting it to wait till someone gets the point later, maybe even too late.

Continue reading “bk AHC: Relevance.”

bk AHC: Why handwriting?

An excerpt from the book Advanced Handwriting Cryptography..
full book https://sellfy.com/p/ujMc / free examples https://sellfy.com/p/HQH3

The reason to keep developing the methods of handwriting cryptography even after the beginning of computer security age is the impossibility to rely on computer encryption only. Whatever a company may claim about impossibility of cracking their code the only secure method is the one having no third party involved (or if shared between several people then no unwanted parties). You can only rely on the method of encryption you yourself have created or customized an existing one. My goal was to develop a method which everyone can modify, to create their own encryption systems while knowing how to do it. I think I have succeeded in the goal, surpassing my own expectations on the security of the method, and you’re going to see it for yourself.

Continue reading “bk AHC: Why handwriting?”