• You can choose to see the film on the last page before you begin reading this document

  • CRITERIA FOR THE REALIZATION OF  EXPLICITPASS


    The fundamental point that has inspired the creation of this application is to give the user only the task to define a simple rule, to create all his passwords, lifting it from the burden of storing them somewhere, or worse still remember the passwords to memory

    Secure Password

    ExplicitPass will have to free ourselves from the effort to build, store and remember passwords complicated, leaving us only the task of inventing a simple rule based on which we can build all our passwords with clear and simple words and will have to shoulder the task to encrypt these passwords for us!

    Simple updating Password

    ExplicitPass  will have to allow us to easily update all our passwords with any deadline it will be recommended to us, and all without the need to memorize anything! Not only that, also will allow us to reproduce without problems all the old passwords of all previous periods since we started to use this beautiful app! And if you really want to overdo, it will also enable us to generate all future passwords for all our sites visited.

    Secure Messages

    ExplicitPass extends the ability to encrypt entire messages. Write your plain text private messages. ExplicitPass will encrypt your messages, so only your intended receiver (that shared with you five secret number) can read them.

    Easy of use

    ExplicitPass will also allow us to give him a few simple guidelines setting so that encryption is EXCLUSIVE only for us, making it virtually impossible for others reproduce our encrypted passwords.


    When you adopt ExplicitPass, you have two choices:

    1)   Use EP for only future password.  In this case, You have to remember all your old passwords. 

    2)   You could use EP to change all your old passwords. In this case, you need to remember only the rule, as shown below. 

    Here is an example of how to eliminate our concerns to create password.

    By way of example, we use the following rule: build any plaintext passwords with a word formed from the name of the site followed by username.

    So, if the user, for example, it call Silvana and during the browsing on the Apple site, she decide to register her, her password could be.

    <Apple>Silvana

    If Silvana, browsing on the GotoFish website, decide to register her, her password could be:

    GoToFishSilvana

    With this rule we understand that Silvana, also without having an iron memory, she manage easily to register in "her head" all the password of website at which she want have an account. No more anxiety! At the request of a new password, Silvana can activate the new account applying the following rule:

    <website name>Silvana

    If a year from now when someone asks Silvana: what your password to access the site of Apple? She answers without hesitation: AppleSilvana .... but obviously!

    Awesome yes, but where is the security?

    Don't worry, "the dirty work" we do to do to ExplixitPass!

    It's a simple software, that use a single page for interact with us and that manages to get us in few seconds, in "the tip of the finger" the most disgusting password that a "password stealer" can imagine.

    But how, if our password are very simple and easy to guess that also a child would be able to discover without much effort?

    It is, but we don't have reckoned without ExplicitPass. The idea is to give to this app our beautiful and easy password, that we call plaintext password, and ask it to encrypt exclusively for us to give us the corresponding encrypted password.

    The result will be a such mixture of characters that you better don't read in order don't have upset stomach, but that a simple touch, copy/paste, we can get it on the "tip of the finger" and transfer it "on the fly" to form that requires access to the Internet.

    It remains to clarify one point: how we doing to tell to ExplicitPass encrypt exclusively, just for us, passwords immaculate that we deliver it and he gives us so disfigured as to be unrecognizable?

    Easy, ExplicitPass is set to receive from us five integers, which it calls keys and jealously hides "in his bosom" at the sight of prying eyes, hastily deleting them, immediately after insertion. Of these combinations of five numbers, there are about 561 billion, so there is virtually no chance that some malicious user can decipher the plaintext password of Silvana, since she has entered its five keys in secret and she has hidden in a very safe place (perhaps in her head!).

    And when we are asked to change the password as we behave?

    The second pillar of this application, as well as the rule for building the password in the clear, is to have the immediate availability of all past passwords, present and even future, without having to write or remember anything by heart. We will see how this is possible with the example shown later.

    It should be noted that some sites place restrictions on the construction of passwords, especially they don't allow the use of the safest special characters UNICODE. For this reason ExplicitPass provides the use of 5 alphabets of increasing complexity for each of which it is possible to use the option constraints that ensures, in the ciphertext, the presence of at least two uppercase two lowercase letters and two numeric digits.

    Of the five alphabets used to encrypt password only the first (Alphabet 1) does not use special characters and is available for the few sites that do not allow passwords with these characters. However, when possible, the most secure passwords are generated with Alphabet 5 associated with the option constraints.