Batch Peg Digital Sign with airSlate SignNow

Batch peg digital sign

OpenSSL is a toolkit used in TLS and the older ssl what this means is when you see a padlock in your address bar in a browser it means it uses one of these protocols what it does is it encrypts content to and from the server to the browser because it's a lot like digital signatures we can actually use some of the functions because open SSL is also a general-purpose cryptography library so in the documentation and the manual pages we can see a list of commands so we'll be using some of these commands to generate a private key from that generate a public key get a message encrypt it you can download it it should be installed on a Mac but you can download it from here if you have Windows or some other operating system that doesn't have it installed so using the open SSL toolkit we can run through generating a digital signature so first I start off with a private key so using the open SSL command generate a private key and specifying an algorithm of RSA and we need to specify the output file we just call it private key door pen and if we list as our private key to generate a public key we need to use the private key so we use open SSL again we do public key and we need to specify the private key which is the input for the public key and then we need to specify the public key output which would be let's just call it public that's our private key and that's our public key now in order to generate a signature we'll need a document so let's just create something simple let's just say a 1000 satoshis let's call it a contract text file so now using our private key we can create a digital signature of the contract we use open SSL so we want to create a digest using sha-256 sign using our private key and we want our output so this will be the actual digital signature we'll just call it signature this could be anything you want to call it and the file that we're using to sign is contract so now if we check out signature you see it's a binary file so a signature is binary there is a way to output it as a hexadecimal file but for this example we'll just keep it as binary so now to verify the signature we will still use digest and sha-256 but now we'll verify using the public key and we specify the signature we're using to verify and then the year original contract if we modify the contract in anywhere let's say I want to not pay or Bob wants to not pay me as much as a thousand so he's going to modify the original file so now when I come to verify the signature the verification has changed because the digest is a hash of the document so if that document even changes one bit the entire digest will be completely different the hash will be completely different so we can verify that the person with the private key actually signed that document because we can decrypt it or we can verify it using their public key