Encrypting then Base64 Encoding












3















I notice online encryption tools encrypt the plaintext and output the ciphertext in base64 format. Why is ciphertext outputted in base64 format? Can the ciphertext be outputted in binary format?






encryption cryptography







share|improve this question























  • You can translate that data into any base, it just happens that Base64 is well suited for the web; it's composed of characters that are safe to use in URLs.

    – meagar
    4 hours ago
















3















I notice online encryption tools encrypt the plaintext and output the ciphertext in base64 format. Why is ciphertext outputted in base64 format? Can the ciphertext be outputted in binary format?






encryption cryptography







share|improve this question























  • You can translate that data into any base, it just happens that Base64 is well suited for the web; it's composed of characters that are safe to use in URLs.

    – meagar
    4 hours ago














3












3








3








I notice online encryption tools encrypt the plaintext and output the ciphertext in base64 format. Why is ciphertext outputted in base64 format? Can the ciphertext be outputted in binary format?






encryption cryptography







share|improve this question














I notice online encryption tools encrypt the plaintext and output the ciphertext in base64 format. Why is ciphertext outputted in base64 format? Can the ciphertext be outputted in binary format?






encryption cryptography




encryption cryptography






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 5 hours ago









Angela LipfordAngela Lipford

282




282













  • You can translate that data into any base, it just happens that Base64 is well suited for the web; it's composed of characters that are safe to use in URLs.

    – meagar
    4 hours ago



















  • You can translate that data into any base, it just happens that Base64 is well suited for the web; it's composed of characters that are safe to use in URLs.

    – meagar
    4 hours ago

















You can translate that data into any base, it just happens that Base64 is well suited for the web; it's composed of characters that are safe to use in URLs.

– meagar
4 hours ago





You can translate that data into any base, it just happens that Base64 is well suited for the web; it's composed of characters that are safe to use in URLs.

– meagar
4 hours ago










2 Answers
2






active

oldest

votes


















1














A web browser has to print a visual representation of the binary data. The usual visual representation of binary data is the hexadecimal notation.



Now observe: The space overhead of hex-encoded data is factor 2 (we need 2 ascii characters for one byte).
The space overhead of base64-encoded data is only 1.33, making it more space-efficient than hex-encoded data.



Moreover, I suspect that the tool support for base64-encoded data is at least as good as for hex-encoded data.



For instance, you can copy-paste a base64-encoded ciphertext directly into a PEM file.






share|improve this answer

































    1














    Ciphertext can be output in binary format. For example, gpg defaults to binary format, and you need to specify --armor to make it base64:



    --armor
    
-a
    
    Create ASCII armored output. The default is to create the binary OpenPGP format.


    The reason you see ASCII/base64 more often is that it is easier to transfer and manipulate than binary. SMTP email, for example, cannot handle binary data without encoding it, so having a non-binary format makes it simpler to email encrypted text. FTP may default to non-binary mode which will introduce errors when transferring a binary file. Even something as simple as popping open a file in an editor to make sure it "looks like it's there" is easier with non-binary formats.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "162"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      noCode: true, onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f205536%2fencrypting-then-base64-encoding%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      A web browser has to print a visual representation of the binary data. The usual visual representation of binary data is the hexadecimal notation.



      Now observe: The space overhead of hex-encoded data is factor 2 (we need 2 ascii characters for one byte).
      The space overhead of base64-encoded data is only 1.33, making it more space-efficient than hex-encoded data.



      Moreover, I suspect that the tool support for base64-encoded data is at least as good as for hex-encoded data.



      For instance, you can copy-paste a base64-encoded ciphertext directly into a PEM file.






      share|improve this answer






























        1














        A web browser has to print a visual representation of the binary data. The usual visual representation of binary data is the hexadecimal notation.



        Now observe: The space overhead of hex-encoded data is factor 2 (we need 2 ascii characters for one byte).
        The space overhead of base64-encoded data is only 1.33, making it more space-efficient than hex-encoded data.



        Moreover, I suspect that the tool support for base64-encoded data is at least as good as for hex-encoded data.



        For instance, you can copy-paste a base64-encoded ciphertext directly into a PEM file.






        share|improve this answer




























          1












          1








          1







          A web browser has to print a visual representation of the binary data. The usual visual representation of binary data is the hexadecimal notation.



          Now observe: The space overhead of hex-encoded data is factor 2 (we need 2 ascii characters for one byte).
          The space overhead of base64-encoded data is only 1.33, making it more space-efficient than hex-encoded data.



          Moreover, I suspect that the tool support for base64-encoded data is at least as good as for hex-encoded data.



          For instance, you can copy-paste a base64-encoded ciphertext directly into a PEM file.






          share|improve this answer















          A web browser has to print a visual representation of the binary data. The usual visual representation of binary data is the hexadecimal notation.



          Now observe: The space overhead of hex-encoded data is factor 2 (we need 2 ascii characters for one byte).
          The space overhead of base64-encoded data is only 1.33, making it more space-efficient than hex-encoded data.



          Moreover, I suspect that the tool support for base64-encoded data is at least as good as for hex-encoded data.



          For instance, you can copy-paste a base64-encoded ciphertext directly into a PEM file.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 4 hours ago

























          answered 4 hours ago









          Mike76Mike76

          15119




          15119

























              1














              Ciphertext can be output in binary format. For example, gpg defaults to binary format, and you need to specify --armor to make it base64:



              --armor
              
-a
              
    Create ASCII armored output. The default is to create the binary OpenPGP format.


              The reason you see ASCII/base64 more often is that it is easier to transfer and manipulate than binary. SMTP email, for example, cannot handle binary data without encoding it, so having a non-binary format makes it simpler to email encrypted text. FTP may default to non-binary mode which will introduce errors when transferring a binary file. Even something as simple as popping open a file in an editor to make sure it "looks like it's there" is easier with non-binary formats.






              share|improve this answer




























                1














                Ciphertext can be output in binary format. For example, gpg defaults to binary format, and you need to specify --armor to make it base64:



                --armor
                
-a
                
    Create ASCII armored output. The default is to create the binary OpenPGP format.


                The reason you see ASCII/base64 more often is that it is easier to transfer and manipulate than binary. SMTP email, for example, cannot handle binary data without encoding it, so having a non-binary format makes it simpler to email encrypted text. FTP may default to non-binary mode which will introduce errors when transferring a binary file. Even something as simple as popping open a file in an editor to make sure it "looks like it's there" is easier with non-binary formats.






                share|improve this answer


























                  1












                  1








                  1







                  Ciphertext can be output in binary format. For example, gpg defaults to binary format, and you need to specify --armor to make it base64:



                  --armor
                  
-a
                  
    Create ASCII armored output. The default is to create the binary OpenPGP format.


                  The reason you see ASCII/base64 more often is that it is easier to transfer and manipulate than binary. SMTP email, for example, cannot handle binary data without encoding it, so having a non-binary format makes it simpler to email encrypted text. FTP may default to non-binary mode which will introduce errors when transferring a binary file. Even something as simple as popping open a file in an editor to make sure it "looks like it's there" is easier with non-binary formats.






                  share|improve this answer













                  Ciphertext can be output in binary format. For example, gpg defaults to binary format, and you need to specify --armor to make it base64:



                  --armor
                  
-a
                  
    Create ASCII armored output. The default is to create the binary OpenPGP format.


                  The reason you see ASCII/base64 more often is that it is easier to transfer and manipulate than binary. SMTP email, for example, cannot handle binary data without encoding it, so having a non-binary format makes it simpler to email encrypted text. FTP may default to non-binary mode which will introduce errors when transferring a binary file. Even something as simple as popping open a file in an editor to make sure it "looks like it's there" is easier with non-binary formats.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 57 mins ago









                  gowenfawrgowenfawr

                  53.7k11114159




                  53.7k11114159






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Information Security Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid …



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f205536%2fencrypting-then-base64-encoding%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      -

                      Popular posts from this blog

                      How to label and detect the document text images

                      Image
                      1 $begingroup$ This is what I mean as document text image: I want to label the texts in image as separate blocks and my model should detect these labels as classes. NOTE: This is how the end result should be like: The labels like Block 1, Block 2, Block 3,.. should be Logo, Title, Date,.. Others, etc. Work done: First approach : I tried to implement this method via Object Detection, it didn't work. It didn't even detect any text. Second approach : Then I tried it using PixelLink. As this model is build for scene text detection, it detected each and every text in the image. But this method can detect multiple lines of text if the threshold values are increased. But I have no idea how do I add labels to the text blocks. PIXEL_CLS_WEIGHT_all_ones = 'PIXEL_CLS_WEIGHT_all_ones' PIXEL_C...
                      Read more

                      Vallis Paradisi

                      Image
                      Coordinata: .mw-parser-output .geo-default,.mw-parser-output .geo-dms,.mw-parser-output .geo-dec{display:inline}.mw-parser-output .geo-nondefault,.mw-parser-output .geo-multi-punct{display:none}.mw-parser-output .longitude,.mw-parser-output .latitude{white-space:nowrap} 33°03′S 71°37′W  /  33.05°S 71.617°W  / -33.05; -71.617 Vallis Paradisi Res apud Vicidata repertae: Civitas : Chilia Numerus incolarum : 296 655 Zona horaria : UTC-4 Situs interretialis Nomen officiale : Valparaíso Gubernium Consilium : municipal council of Valparaíso Geographia Superficies : 401 600 000 Metrum quadratum Coniunctiones urbium Urbes gemellae : Ovetum , Badalona , Santa Fe , Ora longa , Sciamhaevum , Quantunia , Callao , Bat Yam , Melaka , Novorossiysk , Busan , Corduba , Odessa , Rosario , Malacca , Barcino , Soteropolis , Franciscopolis (California) , Guanajuato, Silao Tabula aut despectus Despectus in portum sinumque et urbem Vallis Paradisi Vallis Para...
                      Read more

                      Tabula Rosettana

                      Image
                      Tabula multilinguis Rosettana in Museo Britannico ostenditur. Tabula Rosettana, [1] etiam titulo OGIS 90 agnita, est stela decreto de rebus sacris in Aegypto anno 196 a.C.n. lato inscripta. Tabula iuxta Rosettam Aegypti, urbem in delta Nili et ad oram maris Mediterranei iacentem, anno 1799 a milite Francico reperta est. Inventio stelae, linguis duabus scripturisque tribus inscriptae, eruditis Instituti Aegypti statim nuntiata est; ibi enim iussu imperatoris Napoleonis eruditi omnium scientiarum (sub aegide Commissionis Scientiarum et Artium) properaverant cum expeditione Francica. Qua a Britannis mox debellata, tabula Rosettana Londinium missa hodie apud Museum Britannicum iacet. Textus Graecus cito lectus interpretationi textuum Aegyptiorum (in formis hieroglyphica et demotica expressorum) gradatim adiuvit. Denique textum plene interpretatus est Ioannes Franciscus Champollion. Ab opere eruditorum cumulativo coepit hodiernus scripturae hieroglyphicae linguaeque Aegyptiae a...
                      Read more