0 оценок0% нашли этот документ полезным (0 голосов)
66 просмотров7 страниц
The document proposes a project called TSEC to provide secure SMS and voice communication using the GSM network. The project will use AES-256/128 encryption with an additional proprietary algorithm for added security. It will have two phases: phase 1 focuses on encrypted SMS functionality in 2 weeks, and phase 2 adds encrypted call functionality in 4 weeks. The encryption will occur at the application level on Android and Windows Phone. A block diagram and SMS encryption flowchart show data/voice will be encrypted before transmission and decrypted by the receiver. Users will need to authenticate with a password before being able to select encryption and add encryption keys for contacts to enable secure communication.
The document proposes a project called TSEC to provide secure SMS and voice communication using the GSM network. The project will use AES-256/128 encryption with an additional proprietary algorithm for added security. It will have two phases: phase 1 focuses on encrypted SMS functionality in 2 weeks, and phase 2 adds encrypted call functionality in 4 weeks. The encryption will occur at the application level on Android and Windows Phone. A block diagram and SMS encryption flowchart show data/voice will be encrypted before transmission and decrypted by the receiver. Users will need to authenticate with a password before being able to select encryption and add encryption keys for contacts to enable secure communication.
The document proposes a project called TSEC to provide secure SMS and voice communication using the GSM network. The project will use AES-256/128 encryption with an additional proprietary algorithm for added security. It will have two phases: phase 1 focuses on encrypted SMS functionality in 2 weeks, and phase 2 adds encrypted call functionality in 4 weeks. The encryption will occur at the application level on Android and Windows Phone. A block diagram and SMS encryption flowchart show data/voice will be encrypted before transmission and decrypted by the receiver. Users will need to authenticate with a password before being able to select encryption and add encryption keys for contacts to enable secure communication.
Group Members Capt Irfan Tasneem Capt Jamal Ahmed Capt Ehsan Ullah
Intro 1. TSEC is an idea for secure SMS/voice comm using GSM network. It will provide end to end comm security thus making use of public GSM network possible, once required, in a secure manner. Note that the security of any cryptographic algorithm depends upon Cryptographic Algorithm and the key including its exchange. For public utilities std public algorithms (algorithm is known to everyone) rely on the security of key only. In this project we will be utilizing publically known secure ciphers i-e AES. However for add-on security, our algorithm will be secret which would do just certain customization on the output of AES. Special emphasis will be given to ensure adequate attn to ensure security in the overall execution of the project. Salient aspects for this project are:- a. Encryption Std - AES-256/AES-128 (Output of AES can be further customized for add-on security) b. Time Line. i. Ph-1 - Encrypted SMS Functionality(2 weeks) ii. Ph-2 - Encrypted Call Functionality (4 weeks ) c. Encryption - Application level d. Platform - Android / Windows Phone
2. Detailed options and possibilities for this application are att for review/approval. Initial focus will be on the text/SMS based encryption.
Block Diagram 3. Data/Voice will be encrypted before transmission. Therefore receivers in between even the GSM network will not be able to get the content of the data in transition. It would be decrypted after being received by the receiver.
4. Users will open the TSEC application. Password will be required to open the application, unauthenticated users will be able to send messages in plain mode. For authenticated users, they will have the option to use encryption or not. 5. In settings mode, users will be able to add the encryption key for each contact in their contact list which will be used to carryout secure comm with the members in the contact list. Password of the user will be used to store the encryption keys in encrypted way. 6. User will write an sms for user A. Encryption key of the recipient will be used to encrypt the sms/call and will be transmitted, later the recipient of the user will use its own key to decrypt the message/call.
Encrypted
SMS Encryption Flow Chart
Admin Panel
Keys Exchange 7. Keys for the registered users will be issued along with the password by GHQ. 8. Keys be generated by the application using Pseudo Random Generators and shared securely using RSA (asymmetric, public-private key).
Echo on a Chip - Secure Embedded Systems in Cryptography: A New Perception for the Next Generation of Micro-Controllers handling Encryption for Mobile Messaging