datatracker.ietf.org/doc/html/rfc4086.html

Preview meta tags from the datatracker.ietf.org website.

Linked Hostnames

8

Thumbnail

Search Engine Appearance

Google

https://datatracker.ietf.org/doc/html/rfc4086.html

RFC 4086: Randomness Requirements for Security

Randomness Requirements for Security (RFC 4086, )



Bing

RFC 4086: Randomness Requirements for Security

https://datatracker.ietf.org/doc/html/rfc4086.html

Randomness Requirements for Security (RFC 4086, )



DuckDuckGo

https://datatracker.ietf.org/doc/html/rfc4086.html

RFC 4086: Randomness Requirements for Security

Randomness Requirements for Security (RFC 4086, )

  • General Meta Tags

    11
    • title
      RFC 4086 - Randomness Requirements for Security
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width, initial-scale=1
    • description
      Randomness Requirements for Security (RFC 4086, )
  • Open Graph Meta Tags

    10
    • og:title
      RFC 4086: Randomness Requirements for Security
    • og:url
      https://datatracker.ietf.org/doc/html/rfc4086.html
    • og:site_name
      IETF Datatracker
    • og:description
      Security systems are built on strong cryptographic algorithms that foil pattern analysis attempts. However, the security of these systems is dependent on generating secret quantities for passwords, cryptographic keys, and similar quantities. The use of pseudo-random processes to generate secret quantities can result in pseudo-security. A sophisticated attacker may find it easier to reproduce the environment that produced the secret quantities and to search the resulting small set of possibilities than to locate the quantities in the whole of the potential number space. Choosing random quantities to foil a resourceful and motivated adversary is surprisingly difficult. This document points out many pitfalls in using poor entropy sources or traditional pseudo-random number generation techniques for generating such quantities. It recommends the use of truly random hardware techniques and shows that the existing hardware on many systems can be used for this purpose. It provides suggestions to ameliorate the problem when a hardware solution is not available, and it gives examples of how large such quantities need to be for some applications. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
    • og:type
      article
  • Twitter Meta Tags

    1
    • twitter:card
      summary_large_image
  • Link Tags

    12
    • alternate
      /feed/document-changes/rfc4086/
    • apple-touch-icon
      https://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-180.png
    • canonical
      https://datatracker.ietf.org/doc/html/rfc4086.html
    • icon
      https://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-32.png
    • icon
      https://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-16.png

Emails

4

Links

47