Is openssl rand command cryptographically secure?Can a PRNG with a fixed amount of entropy always be detected?What stops the Multiply-With-Carry RNG from being a Cryptographically Secure PRNG?Is a Mersenne-twister cryptographically secure if I truncate the output?How Brittle Are LCG-Cracking Techniques?ECC considered secure in OpenSSL?Is this JS library using openssl genrsa -rand improperly?Cryptographic random numbers for key generationLink between openssl 'req' command and 'unable to get local issuer certificate'?openssl command line equivalent of AESWrap? (defined in RFC3394; use in AmazonS3 Client Side Encryption of datakey wrapping)The “openssl genrsa” command only generates a private key?

Multi tool use
Multi tool use

Will a top journal at least read my introduction?

How can I practically buy stocks?

Phrase for the opposite of "foolproof"

Why is it that the natural deduction method can't test for invalidity?

Do I have an "anti-research" personality?

How to make a pipeline wait for end-of-file or stop after an error?

French for 'It must be my imagination'?

How to creep the reader out with what seems like a normal person?

What do the phrase "Reeyan's seacrest" and the word "fraggle" mean in a sketch?

Packing rectangles: Does rotation ever help?

How to verbalise code in Mathematica?

Reducing vertical space in stackrel

How much cash can I safely carry into the USA and avoid civil forfeiture?

Which big number is bigger?

simple conditions equation

Sci-fi book: portals appear in London and send a failed artist towards a designated path where he operate a giant superweapon

Mac Pro install disk keeps ejecting itself

Sci-fi novel series with instant travel between planets through gates. A river runs through the gates

What route did the Hindenburg take when traveling from Germany to the U.S.?

Binary Numbers Magic Trick

Don’t seats that recline flat defeat the purpose of having seatbelts?

How do I use proper grammar in the negation of "have not" for the following sentence translation?

How to pronounce 'C++' in Spanish

a sore throat vs a strep throat vs strep throat



Is openssl rand command cryptographically secure?


Can a PRNG with a fixed amount of entropy always be detected?What stops the Multiply-With-Carry RNG from being a Cryptographically Secure PRNG?Is a Mersenne-twister cryptographically secure if I truncate the output?How Brittle Are LCG-Cracking Techniques?ECC considered secure in OpenSSL?Is this JS library using openssl genrsa -rand improperly?Cryptographic random numbers for key generationLink between openssl 'req' command and 'unable to get local issuer certificate'?openssl command line equivalent of AESWrap? (defined in RFC3394; use in AmazonS3 Client Side Encryption of datakey wrapping)The “openssl genrsa” command only generates a private key?













5












$begingroup$


I'm wondering if the openssl rand command produces cryptographically secure random bytes. For example when in need for a random password or token:



openssl rand -hex 32


The man page unfortunately does neither state it's cryptographically secure, nor that it's not.



On the one hand, I think this is openssl, its sole purpose is to do cryptography. On the other hand, the man page states something about reading and writing seed data instead of directly querying a CSPRNG.



So it is somewhat unclear for the end user. Does someone know?










share|improve this question









$endgroup$
















    5












    $begingroup$


    I'm wondering if the openssl rand command produces cryptographically secure random bytes. For example when in need for a random password or token:



    openssl rand -hex 32


    The man page unfortunately does neither state it's cryptographically secure, nor that it's not.



    On the one hand, I think this is openssl, its sole purpose is to do cryptography. On the other hand, the man page states something about reading and writing seed data instead of directly querying a CSPRNG.



    So it is somewhat unclear for the end user. Does someone know?










    share|improve this question









    $endgroup$














      5












      5








      5


      1



      $begingroup$


      I'm wondering if the openssl rand command produces cryptographically secure random bytes. For example when in need for a random password or token:



      openssl rand -hex 32


      The man page unfortunately does neither state it's cryptographically secure, nor that it's not.



      On the one hand, I think this is openssl, its sole purpose is to do cryptography. On the other hand, the man page states something about reading and writing seed data instead of directly querying a CSPRNG.



      So it is somewhat unclear for the end user. Does someone know?










      share|improve this question









      $endgroup$




      I'm wondering if the openssl rand command produces cryptographically secure random bytes. For example when in need for a random password or token:



      openssl rand -hex 32


      The man page unfortunately does neither state it's cryptographically secure, nor that it's not.



      On the one hand, I think this is openssl, its sole purpose is to do cryptography. On the other hand, the man page states something about reading and writing seed data instead of directly querying a CSPRNG.



      So it is somewhat unclear for the end user. Does someone know?







      random-number-generator openssl






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 20 at 14:51









      firefexxfirefexx

      1624




      1624




















          1 Answer
          1






          active

          oldest

          votes


















          5












          $begingroup$

          Yes, it is cryptographically secure, pseudo random output, seeded by retrieving secure random data from the operating system.



          If it is random or not depends on the fact if the OS RNG is random. This is usually the case on normal desktops, but you'd better be sure for e.g. limited embedded systems. If no truly random data can be retrieved - according to RAND_bytes - then rand will exit with an error.




          Any random source that you add using -rand [file][:file]* is used as additional seed data - in other words, the output will always be random, even if you supply the same seed.



          As the pseudo random generator provided by OpenSSL generally runs in the application space on the main thread, it may be faster than asking a lot of data from /dev/urandom. But to be honest, most of the time using /dev/urandom suffices (and current implementations are pretty fast as well).




          You can see that it is random when you look at the link to the RAND_bytes manual page which is the function that lies behind command line rand and is linked to from the manual page (in the "see also section, but yeah"):




          RAND_bytes() puts num cryptographically strong pseudo-random bytes into buf. An error occurs if the PRNG has not been seeded with enough randomness to ensure an unpredictable byte sequence.




          That RAND_bytes() is used can be found in the source file for the rand command, rand.c, so yes, this is indeed the function that is called.






          share|improve this answer











          $endgroup$













            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "281"
            ;
            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%2fcrypto.stackexchange.com%2fquestions%2f68919%2fis-openssl-rand-command-cryptographically-secure%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            5












            $begingroup$

            Yes, it is cryptographically secure, pseudo random output, seeded by retrieving secure random data from the operating system.



            If it is random or not depends on the fact if the OS RNG is random. This is usually the case on normal desktops, but you'd better be sure for e.g. limited embedded systems. If no truly random data can be retrieved - according to RAND_bytes - then rand will exit with an error.




            Any random source that you add using -rand [file][:file]* is used as additional seed data - in other words, the output will always be random, even if you supply the same seed.



            As the pseudo random generator provided by OpenSSL generally runs in the application space on the main thread, it may be faster than asking a lot of data from /dev/urandom. But to be honest, most of the time using /dev/urandom suffices (and current implementations are pretty fast as well).




            You can see that it is random when you look at the link to the RAND_bytes manual page which is the function that lies behind command line rand and is linked to from the manual page (in the "see also section, but yeah"):




            RAND_bytes() puts num cryptographically strong pseudo-random bytes into buf. An error occurs if the PRNG has not been seeded with enough randomness to ensure an unpredictable byte sequence.




            That RAND_bytes() is used can be found in the source file for the rand command, rand.c, so yes, this is indeed the function that is called.






            share|improve this answer











            $endgroup$

















              5












              $begingroup$

              Yes, it is cryptographically secure, pseudo random output, seeded by retrieving secure random data from the operating system.



              If it is random or not depends on the fact if the OS RNG is random. This is usually the case on normal desktops, but you'd better be sure for e.g. limited embedded systems. If no truly random data can be retrieved - according to RAND_bytes - then rand will exit with an error.




              Any random source that you add using -rand [file][:file]* is used as additional seed data - in other words, the output will always be random, even if you supply the same seed.



              As the pseudo random generator provided by OpenSSL generally runs in the application space on the main thread, it may be faster than asking a lot of data from /dev/urandom. But to be honest, most of the time using /dev/urandom suffices (and current implementations are pretty fast as well).




              You can see that it is random when you look at the link to the RAND_bytes manual page which is the function that lies behind command line rand and is linked to from the manual page (in the "see also section, but yeah"):




              RAND_bytes() puts num cryptographically strong pseudo-random bytes into buf. An error occurs if the PRNG has not been seeded with enough randomness to ensure an unpredictable byte sequence.




              That RAND_bytes() is used can be found in the source file for the rand command, rand.c, so yes, this is indeed the function that is called.






              share|improve this answer











              $endgroup$















                5












                5








                5





                $begingroup$

                Yes, it is cryptographically secure, pseudo random output, seeded by retrieving secure random data from the operating system.



                If it is random or not depends on the fact if the OS RNG is random. This is usually the case on normal desktops, but you'd better be sure for e.g. limited embedded systems. If no truly random data can be retrieved - according to RAND_bytes - then rand will exit with an error.




                Any random source that you add using -rand [file][:file]* is used as additional seed data - in other words, the output will always be random, even if you supply the same seed.



                As the pseudo random generator provided by OpenSSL generally runs in the application space on the main thread, it may be faster than asking a lot of data from /dev/urandom. But to be honest, most of the time using /dev/urandom suffices (and current implementations are pretty fast as well).




                You can see that it is random when you look at the link to the RAND_bytes manual page which is the function that lies behind command line rand and is linked to from the manual page (in the "see also section, but yeah"):




                RAND_bytes() puts num cryptographically strong pseudo-random bytes into buf. An error occurs if the PRNG has not been seeded with enough randomness to ensure an unpredictable byte sequence.




                That RAND_bytes() is used can be found in the source file for the rand command, rand.c, so yes, this is indeed the function that is called.






                share|improve this answer











                $endgroup$



                Yes, it is cryptographically secure, pseudo random output, seeded by retrieving secure random data from the operating system.



                If it is random or not depends on the fact if the OS RNG is random. This is usually the case on normal desktops, but you'd better be sure for e.g. limited embedded systems. If no truly random data can be retrieved - according to RAND_bytes - then rand will exit with an error.




                Any random source that you add using -rand [file][:file]* is used as additional seed data - in other words, the output will always be random, even if you supply the same seed.



                As the pseudo random generator provided by OpenSSL generally runs in the application space on the main thread, it may be faster than asking a lot of data from /dev/urandom. But to be honest, most of the time using /dev/urandom suffices (and current implementations are pretty fast as well).




                You can see that it is random when you look at the link to the RAND_bytes manual page which is the function that lies behind command line rand and is linked to from the manual page (in the "see also section, but yeah"):




                RAND_bytes() puts num cryptographically strong pseudo-random bytes into buf. An error occurs if the PRNG has not been seeded with enough randomness to ensure an unpredictable byte sequence.




                That RAND_bytes() is used can be found in the source file for the rand command, rand.c, so yes, this is indeed the function that is called.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Apr 20 at 17:09

























                answered Apr 20 at 16:18









                Maarten BodewesMaarten Bodewes

                56.3k679197




                56.3k679197



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Cryptography 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.

                    Use MathJax to format equations. MathJax reference.


                    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%2fcrypto.stackexchange.com%2fquestions%2f68919%2fis-openssl-rand-command-cryptographically-secure%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







                    Oa8,ZixN75Z
                    f 9 cYHz0cU1UQPYqvNMyTh,x W2HRSY kHU73R J9c,uGWZ,twzKPO yhMVNMQEe Sd8RPnSY1F6IgI25pJkRfCclA

                    Popular posts from this blog

                    RemoteApp sporadic failureWindows 2008 RemoteAPP client disconnects within a matter of minutesWhat is the minimum version of RDP supported by Server 2012 RDS?How to configure a Remoteapp server to increase stabilityMicrosoft RemoteApp Active SessionRDWeb TS connection broken for some users post RemoteApp certificate changeRemote Desktop Licensing, RemoteAPPRDS 2012 R2 some users are not able to logon after changed date and time on Connection BrokersWhat happens during Remote Desktop logon, and is there any logging?After installing RDS on WinServer 2016 I still can only connect with two users?RD Connection via RDGW to Session host is not connecting

                    Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

                    Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020