Fax Assignee Digital Signature with airSlate SignNow

Fax assignee digital signature

hello my name is asahi kantu and this is assignment number three for network security and vulnerability subject in this assignment i will show you how i implemented a digital signature scheme i will show you the analysis and results of the assignment in the public key infrastructure emulation in a very simplistic way and how i managed to implement a server application client application and the log file generations to transmit information over two different endpoints first of all let's see how the digital signature scheme works for my project let's assume alice is a user above another user and both want to send and receive information each other and validate its authenticity as well as confirm that each user sent the information and it hasn't been altered over its transmission so alice beforehand makes use of an algorithm for asymmetric key generation which in this case is rsa 1024 to generate a private key and a public key alice then can transmit over the network his her public key through bob and bob can store it for later usage then alice chooses his her data and passes through a hashing algorithm which in this case is shot 512. once this information has been hashed it is encrypted by using her private key which later on generates a digital signature after alice has performed these tasks both pieces of information can be sent together over the network where bob receives it and then the inverse procedure takes effect to just confirm that the original data is authentic so in order to do so bob passes the same piece of data over the same hashing algorithm sha 512 and generates a hash and at the same time the digital signature sent by alice is decrypted by using alice's public key which is well generates another hash by comparing those hashes and making sure both are equal we can confirm the authenticity of the document now the way this workflow works and the reason why this works is because the only way to decrypt such information i get the same information that alice's hashed the original document is by decrypting with alice's public key once it has been encrypted with her private key by using any other key this decryption wouldn't be possible or it will just create pure noise unreadable messages so to summarize again the algorithms i implemented was rsa 1024 for asymmetric key generation public and private key generation and sha 512 for hashing and creating the digital signatures before we run through the demo i will show you which tools i used for this project first of all i created a server application using flask and socket io which basically coordinates all the information transmitted between alice and bob or any to any any other end entity this server works at the coordination and it's assumed it runs over a secure channel and both users trust over this server emulating a certificate authority or a very high authority uh confirming that information travels in a secure channel for the client application i used wx python for the graphical user interface i use the key exchange algorithm running with through socket io the digital signature or the hashing algorithm sha 512 and the asymmetric key generation rsa 1024 let me show you now how this works first of all let's just take a look at the server application as you can see it just consists of flask socket ios and through different methods it coordinates and receives the information requested by different users by creating communication channels it makes sure the information arrives to the specified user on the client side all the implementation runs through a graphical user interface and makes use as well of socket io to transmit the information over the server once the application has been connected it is important to mention that client makes use of dss algorithm which implements crypto dome python package on this module this python module makes use of generation of public keys and decomposes to be able to send them over the network it also makes sure that the document or the information is properly signed and verified so the users who employ the client application can make use of this dss module to perform the authentication and validation operation and now let's just run the code first i will run the server and we will assume this server is a trusted authority which transmits communication over a secure channel and then users wants to start a session with this server where they want to transmit information to be verified following the digital signature schematics assume this user is alice and she connects to the server once alice has started session with the server the algorithm generates a private key and public key let's do the same for bob and we see now that bob as well has created his private and public keys now what the server did here is created a transmit to each user the information saying okay that users have been just logged in and if they are available to chat with let's assume now that alice wants to chat with bob and she wants to start the session so alice's request bob's to start the session and she shares her public key but then accepts receives alice's public key ambap transmits as well his public key to alice you can see here that now the connection is established and both can start sending messages so let's assume alice is sending a message to bob then this message is transmitted over the network and you can see here that the message has been has been verified since the message is sent to bob with the hashed or digital signature for block 2 validated and verified based on alice's private public sorry alice's public key bob can do the same and once bob sends information to alice alice can confirm the information is verified and authentic same principle applies whenever if alice wants to send a file to bob in this case let's just assume we sent these requirements to bob then bob will receive this file and the file will be saved in this client requirement if the file wouldn't be authentic or authentified against the digital signature then it wouldn't allow the file to be downloaded and stored in the system as you can see here we have stored the same file called requirements transmitted over the network which corresponds basically to this requirements file on on the other side and behind the wheels what is actually happening is that all users all the information is being locked and transmitted over the network so for the client side we can see here all information and the public key generation as well as the information transmitted over the network same would apply here and the server as well will lock the information about what has happened and stored the keys as a conclusion the development of this project allowed me to understand the digital signature scheme and the asymmetric encryption implementation over a source code and apply it to real solutions it allowed me to understand the complexity of prime numbers and its importance over cryptography i also had the opportunity to build a simple communication application from scratch and validate all the information and confirm that the algorithms actually work and provide powerful tools for us to create secure applications also understand the limitation of latency complexity and reliability over encryption algorithms and the way we try to create applications for final users to make it friendly simpler but strong so thank you very much and we'll see you next time