eSign Radix-64 Made Easy

E sign radix 64

next we will move on to the next topic PGP operation email compatibility what actually email compatibility when BGP is used at least part of the block to be transmitted is encrypted if only the signature service is used then the message digest is encrypted for example with the sender's private key if the confidential service is used the message plus signature are encrypted it may be in one time a symmetric key thus part of all of these resulting block consists of a stream of arbitrary 8-bit however many electronic mail systems only permit the use of blocks consisting or containing of AXI discs to accommodate this restriction pgb provides the service of service of converting the raw 8-bit binary string to yet stream up a printable ASCII characters the scheme used it for this purposes radix 64 version conversion each group of three octet of binary data is mapped into four ASCII characters this format also offends CRC to detect the transmission error the use of radish 64 expands and message by 33% [Music] fortunately the session key and signature portions of this messages are relatively compact and the plaintext messages have been compressed in fact the compression should be more than enough to compensate further at a 64 X function for example if you're going to see an average compression rate ratio maybe 2.0 using a zip if we ignore the relatively small signature and key components the typical overall effect of compression and expansion finally X would be 1.33 in 2.5 m 3x that maybe 0.66 5x thus there is still an overall compression of M about 1/3 so one noteworthy aspect of this radix 64 algorithm is it's blindly converts the input stream of red X 64 format regardless of content even if the input happens to be ASCII text thus if a message is signed but not encrypted and the conversions applied to the n-type block the output will be untreatable to the casual observer which provides a certain level of confidentiality as an option PGP can be configured to convert to radix 64 former only the signature portion of the sign the plaintext message this enables the human recipient to read the message without using PGP PGP would be still have to be used to verify the signature for example the we will see about the particular operation the speaker the relationship among the four services so for what we discussed this could inhibit us and so with it on the transmission generic transmission diagram which is going to be illustrated or it's it's completely stated over here let's see how it's going to be to the operation a bun on transmission a signature is going to be generated using an ash core of the uncompressed to pine text then the bind text plus signature if present is compressed for example a file which is going to be given over there and whenever your signature is going to be required then it can generate the signature and there is going to be concatenated with the file and that is going to became compressed if no signature is required just simply this file is couldn't be get compress Dorothy next if the content shallot is required the block is encrypted and prepared with the public key encrypted symmetric encryption key finally the entire block is converted to ready 16 example for the compression after the compression the data if conference shot is going to be required then we can do the encryption process to provide the confidentiality for this particular operation with the public key with the public key under shared key otherwise if no confidential is going to require stratum it's going to be given for the converter radix 64 this is going to be the operation which is going to be there in the generic transmission diagram we will see a port on the reception end in the reception end once the incoming block is first converted into back from radix 64 format to binary then if message is going to be encrypted then the receptor need to decrypt the information if it is not encrypted then straight away the information may be get taken for the decompression if the message is encrypted then we have to go for the decryption process the decryption process is going to be done with the private key of the user with the particular public key then we have to get the data over here if the message is the resultant block is then be compressed if the message is sign the the receptor recovers the transmitter ash code and compares its to its own calculation of the hash code otherwise straight away that decompressed data will be taken over here this is a generic reception diagram which is going to be present in the particular email compatibility let us discuss about the fifth parameter service of the particular PGP operation segmentation another constraint of the Zeeman is that that is usually a maximum message length and PGP automatically blocks an encrypted message into segments of an appropriate length on the reception the segment's must be reassembled before the decryption process so such a way this PGP is going to be kept operate able under the services as we have come across with this particular thing authentication confidentiality authentication and confidentiality both together and email compatibility sorry compression email compatibility and finally the segmentation process these are the file services which have been provided for the PGP operation let me see the summary of PGP services under the function a digital signature is may be used over there or message encryption compression and email compatibility the algorithm which is going to be used over there the digital signature is going to be T SSR sha on RSA sha and which is going to be providing an ash code of message is created using this SH algorithm the encryption process may be and DSS or RSA which is with the helper position as private key and which includes the message of the message encryption the algorithm it is going to use over there is nothing but C ast 128-bit our IDE or triple key encryption dip triple tree decryption is going to be get used over the with the diffie-hellman RSM so here the description is nothing but the message is encrypted using the particular caste 128 the hi DEA or Triple DES with one time session key generated by the Cinda the center key is encrypted using a DV Hellman or an RSA with the recipients public key and it includes a message the compression method which is going to be used over is nothing but zip xored IP zip compression method so a message may be compressed for storage or transmission using the zip the knee mail compatibility is nothing but we are going to use an ordered x64 conversion method which is going to provide the transparency for email applications as encrypted messages may be converted to en asking strings using in reading 64 conversion such a way we have come to an conclusion summary of this particular video in this particular video we have come across with an introduction about electronic mail security we have entered into we have seen about the pretty good privacy protocol the notations which have been used in the critical privacy and operational descriptions nothing but the services provided by the PGP the five different services authentication confidentiality compression email compatibility and finally segmentation and we are come across with transmission and reception of a message in the PGP in the email compatibility and finally we conclude with the summary of PGP services hope that this video may would be helpful for you people to understand about the PGP operation the pretty good privacy operation which have been used in the email security if you have any queries kindly we can post the chorus to me thank you for watching this video thank you