Email Security

Published on February 2017 | Categories: Documents | Downloads: 49 | Comments: 0 | Views: 265
of 4
Download PDF   Embed   Report

Comments

Content

                                                                                                                                                                                                         Email Security

Email Security
N.Sivanambi, N.Ragavendran Francis Xavier Engineering College, Tirunelveli-627003 [email protected], [email protected] Abstract:
data. Before encryption we introduce compression using code book which contain the short notation of English word, e.g. computer- cmp, encyclopedia-eclpd. The number of letters will be minimizing in size and the message is compressed. Then compressed message is encrypted with key produced by receiver’s ID and send the message over Internet. On receiver’s side key is generated for receiver’s identity and decrypt the message, using code book the message is restore for user [7].

On Internet, securing email has always been an important issue. Various standards and products have been created. There are very rare web services provide the encryption to Emails for security purposes. Data Compression in email is not broadly introduced, by generating code book like telegraphic code book, text message could compress up to 35% to 45%. By using programming techniques it is very easy to Compress, the text message and regenerates original message using same Code book. Sending messages using Code book is traditional method to provide confidentiality. Algorithms of Encryption, Decryption, Compression and Decompression will provide the Security to Email over internet. Even though the key is also define from the receiver user id and the character is converted to cipher text with different key and key incremented by one every time.
Key Word:
Identity based encryption, Code book, and E-mail security.

2. Related Work:
In early Email system everyone should encrypt their e-mail. With identity theft on the rise, should anyone risk passwords, credit card transactions, Social Security numbers, and other sensitive information in an e-mail message? Consider how often transfer companyconfidential information—salaries, vendor bids, purchase transactions, and the like—all via e-mail. Yet most e-mail messages remain unencrypted, even in the face of increasingly sophisticated hackers bent on pillaging con¿dential information for their own gain. Why do most people continue to fail to protect themselves despite the long-time availability of systems based on public-key infrastructure [8]? The answer is simple: PKI is just too difficult for the average user. It requires a tremendous overhead in terms of setting up a public key [6]: locating a certificate authority that can issue a digital certificate to authenticate that public key, somehow publicizing the public key to others, renewing the certificate when it expires, and so on. E-mail senders must also look up a recipient’s public key before encrypting an e-mail. So unless a company mandates the use of encrypted e-mail, this mountain of work is just too much for most people. One proposed solution to this problem is identity-based encryption, which is simpler than PKI because it allows an arbitrary string of characters and numbers to serve as a public key. This simple change in concept has some surprisingly far-reaching effects in simplifying public-key encryption [6]. Adi Shamir, a co-inventor of the RSA public key encryption algorithm, first suggested IBE in 1984

1. Introduction
Who will choose which security standards to use? Who will assure that the technology will be interoperable? Who will decide which records are official government records? Who will decide what level of security assurance is adequate for the privacy protection requirements of different agencies? Who will receive the interagency funding for implementation [1]? Securing E-mails [4] with encryption is introduced broadly by many experts, and they are successful in security matters. Several algorithms are designed for encryption and decryption. But intruders, hackers are still trying to search solution to decrypt the

                                                                                                                                                                                                         Email Security

(“Identity-Based Cryptosystems and Signature Schemes,”Adi Shamir, Proc. Crypto 84 on Advances in Cryptology, Springer-Verlag, 1984) [9]. However, it was not until 2001 that practical implementations were discovered by researchers at Stanford University and the UK government-run Communications-Electronics Security Group. IBE schemes can use any publicly available information in the creation of the public key; such information could be e-mail addresses, Internet Protocol addresses, phone numbers, and dates (to allow for validity periods). Such public and accessible information can serve as an easily knowable public key, so the sender has little overhead in encrypting data, as long as sender and recipient agree to a public-key derivation algorithm --for example, how to format the date or telephone number. IBE systems make use of a centralized key generation center (KGC), which is responsible for the creation and secure distribution of private keys to users. The KGC also issues a set of fixed public parameters called domain parameters. These domain parameters include descriptions of how to transform the identifier into a public key, which hash functions to use, appropriate groups, generator points, and a KGC master public key. All private keys could be provided by the same KGC, which makes the scheme simpler still. However, allowing each company set up its own KGC means that it has total control over the issuing of private keys within the company. This is helpful because now the burden of generating the private keys can go to a designated person within the organization, typically a system administrator. Rather than individual employees figuring out how to obtain a private key, a more cryptography savvy administrator can run a KGC to generate and distribute these private keys. Key generation relies on the person’s public key (which is derived from their online identifier), plus additional, secret information. The KGC authenticates individuals, and, with the same secret information used to derive the domain parameters, generates a private (decryption) key that corresponds to the individual’s identity. Knowledge of one private key does not mean that an individual can decrypt e-mail for any other individual in the same domain. The domain parameters must be authenticated, the same as for a public key in traditional PKI. The KGC administrator could obtain the certificate from VeriSign, for example, but would only have to do it once for the entire company. Despite using a traditional certificate authority like VeriSign, this scenario differs significantly from traditional PKI. A traditional PKI requires individuals to

set up a public- and private-key pair before anyone can encrypt a message to send to them, as greater the number of individuals greater the number of interactions with an outside certificate authority. Using IBE, the domain parameters remain constant for all individuals who obtain their private keys from the same KGC. They remain fixed regardless of whether a sender encrypts information to [email protected] or [email protected]. Reducing the number of lookups has significant economic and computational advantages. In addition, if an individual is in a domain that supports IBE, a sender can encrypt communications to that individual without his cooperation. By having an e-mail address, the individual has a public key. In a transitional PKI scheme an individual can-not unilaterally begin encrypting all miscommunications. The generally hierarchical structure of e-mail addresses falls in line with the concept of a KGC. In a university, for example, student e-mail addresses might look something like [email protected], where Alice is a member of the computer science department. This leads naturally to linking KGCs with particular people within a particular department. For example, the KGC cs.university.edu would issue keys for all members of that department, allowing senders to obtain domain parameters quickly. If constructed correctly, an IBE-based system can offer additional useful features for sending e-mail. For example, consider a system that uses an e-mail address and the date as the public key. By using the date, the system could then automatically generate a private key for each individual, which would work for only one day. This could allow for “encryption into the future,” and would mean that a recipient could not read an e-mail until a given day, because he would have to wait and obtain that day’s private key from his KGC. Such a mechanism would be useful for sending announcements about product releases or salary increases, for example. Until now, IBE in terms of an identity tied to particular individuals a single person. Consider what uses there might be for an identity tied to a group of people. For example, if sending information that only the management team should see, encrypt that message for [email protected]. The KGC then would have to authenticate particular individuals as belonging to that group and grant them the private key for that group. IBE centralizes all of the problems associated with public-key cryptography. This is beneficial to the security manager as it puts them directly

                                                                                                                                                                                                         Email Security

in charge of issuing public keys and policy management, synchronizing validity periods for all employees [2].

3. Proposed Solution:
Compression Algorithm: Traditional methodology for compressed text or messages is based on codes. The code book introduced to compress the letters in word. Algorithm: Step 1: Repeat the step 2 to step 3 until message is not complete. Step 2: Scan word from message using blank space. Step 3: Replace with its corresponding code and add to message. Step 4: stop Encryption Algorithm: Encryption Algorithm is to convert the plaintext to cipher text, and send the cipher text over communication channel. The shared secret key is based on the receiver’s id for Encryption and the key is incremented by one per letter [3] [11]. Algorithm: Step 1: Generate key from Receiver’s mail id. Step 2: Repeat the step 3 to step 4 until compress message in not complete. Step 3: Scan letter from compress message and convert it in cipher text and add to new message. Step 4: Stop. Decryption Algorithm: Decryption Algorithm is to convert the cipher text to plaintext, and decipher it to read the legitimate message. The shared secret key is based on the receiver’s id for Decryption and the key is incremented by one per letter to decryption [3] [11]. Algorithm: Step 1: Generate key from Receiver’s mail id. Step 2: Repeat the step 3 to step 4 until encrypted message in not complete. Step 3: Scan letter from encrypted message and convert it in plaintext and add to new message Step 4: Stop. Decompression Algorithm: The plaintext is converted into original message. For similar operation we need code book to receiver side also.

Algorithm: Step 1: Repeat the step 2 to step 3 until message is not complete. Step 2: Scan word from message using blank space. Step 3: Replace code with its corresponding word and add to message. Step 4: stop. Code Dictionary: The code dictionary is build using array. Specify two arrays, first array contain the original English word from starting position 0 and in second array which for compress code contains the code for respective English word at position 0. Example: Letter Table: A 1 J 10 S 19 B 2 K 11 T 20 C 3 L 12 U 21 D 4 M 13 V 22 E 5 N 14 W 23 F 6 O 15 X 24 G 7 P 16 Y 25 H 8 Q 17 Z 26 I 9 R 18

To: [email protected] Subject: Introduction, I am student of Francis Xavier College. (Total Character = 39) Compressed message: I m std of Frn Xav Col. (Characters in Compressed Message=23) Secret key: a l i c e c o m p a n y c o m 1+12+9+3+5+3+15+13+16+1+14+25+3+15+13 =147 • Compressed message Encrypted with secret key “147” from Receiver ID. • Secret key increment by one per letter for encryption. • Total Characters in Original Message =39 • Total Characters in Compressed Message=23 • Percentage of Compression is, 100-(23/39)*100=100-58.97=41.03%

                                                                                                                                                                                                         Email Security

Comparison: Secure E-mails with Encryption. Compressing the text is minimizing the overload of traffic over communication channel.

Terms

Compression

Proposed method for Email security using Encryption and Compression Yes (Compression up to 40% to 45% Yes

Existing Methods for Email Security

References:
1)
Martin Ferris, “New Email Security Infrastructure” Proceeding of New security Paradigms Workshop, pp. 20-27 August 3-5, 1994. Noel McCullagh, “Securing E-mail with Identity Based Encryption” IT Proc. of IEEE Computer Society 1520-9202/05, May-June 2005. William Stalling, “Cryptography & Network Security Principles and practice” 3rd edition, Pearson Education 2005. P. Zimmerman. “The official PGP user's guide” MIT Press, Cambridge, MA, 1995. Dan Zhou, Joncheng C. Kuo, Susan Older, Shiu-Kai Chin “Formal Development of Secure Email” Proceedings of the 32nd Hawaii IEEE International Conference on System Sciences, 1999.

No Negligible(Few Web site use this technique) Negligible (Few Web site use this technique) No

2)

Encryption

3)

Decryption

Yes Yes (Uncompress in original Message with Lossless) Private Key ( Key is base on Identity of every user)

4)

Uncompress

5)

Key

Public key

Evolution
Using Encryption and Decryption Algorithms and Compression Algorithms we can secured and compressed the every text information and sent it over the Internet. Anyone over the Internet can use or followed the specified process of securing Emails and Compression techniques to provide the secured compressed E-mails. The shared secret key is based on the receiver’s id, so that the intruders or opponents are not able the decipher the message even they have sample of encrypted text or secret key, Because we convert the message into the codes that based codes and then we encrypt the message using secret key that based on receiver’s id which is vary at each letter of text message to avoid the repetition of letter to break the break force analysis. On receiver’s side the cipher text is converted in plaintext which is in the compressed form and we decode it into normal text, get complete message from code book.

6)

S. L Garfinkel, “Public key cryptography” IEEE Journal of Computer, Volume 29, Issue 6, pp. 101104, June 1996.

7) David M. Kreindler, “Email security in clinical
practice: ensuring patient confidentiality”, Journal of Open Medicine, vol. 2, no. 2, pp. E29-34, 2008. 8) M. Hartmann, S. Maseberg, “Replacement of components in public key infrastructures” The 27th Annual Conference of the IEEE IECON ’01, Volume 3, pp.:2012 - 2016, 29 Nov-Dec. 2001. R. Rivest, A. Shamir, and L. Adleman, “A Method for Obtaining Digital Signatures and Public Key Cryptosystems” Communications of the ACM, February 1978.

9)

Conclusion:
In this paper we describe encryption with variable key and compression with code book, compress message must encrypted is needs of today’s E-mail security. The proposed algorithm has the following advantages,

10) R. Rivest, “The MD4 Message Digest Algorithm” Proceedings of 10th Annual International Cryptology Conference on Advances in Cryptology, pp. 303 - 311 Crypto’90, August 1990. 11) R. Rivest, “The RC5 Encryption Algorithm” Proceeding of Second International Workshop on Fast Software Encryption, December 1994.

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close