559 matching pages, found in 149 ms
Ask StyxWritten on your GPU machine; takes a few seconds the first time.
-
rfc-editor.orghttps://www.rfc-editor.org › info › rfc4956RFC 4956: DNS Security (DNSSEC) Opt-In | RFC Editor
More about rfc-editor.org
Jul 27, 2007. … this definition by allowing insecure delegations to exist within an otherwise signed zone without the corresponding NSEC record at the delegation's owner name. These insecure delegations are proven insecure by using a …
-
rfc-editor.orghttps://www.rfc-editor.org › info › rfc7672RFC 7672: SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) | RFC Editor
More about rfc-editor.org
Oct 14, 2015. … Downgrade Attack ........................... 7 1.3.2 . Insecure Server Name without DNSSEC ................. 7 1.3.3 . Sender Policy Does Not Scale ........................ 8 1.3.4 . Too Many Certification Authorities .................. 9 2 . Identifying Applicable TLSA Records ............................. 9 2.1 . DNS Considerations …
-
errata.rfc-editor.orghttps://errata.rfc-editor.org › searchRFC Errata
More about errata.rfc-editor.org
… 20 Section 2 says: Insecure systems MAY chose to crash, be penetrated, etc. It should say: Insecure systems MAY choose to crash, be penetrated, etc. Notes: 'Chose' is the past tense, and …
-
errata.rfc-editor.orghttps://errata.rfc-editor.org › searchRFC Errata
More about errata.rfc-editor.org
… IP-SFS is considered | insecure. The transmission of sensitive data over IP-SFS is strongly | discouraged unless security is provided by higher level protocols. to say: | By its nature of line-of …
-
rfc-editor.orghttps://www.rfc-editor.org › info › bcp240BCP 240 subseries contains 1 RFC | RFC Editor
More about rfc-editor.org
Jan 30, 2025. … less secure or even insecure. Abstract This document describes best current security practice for OAuth 2.0. It updates and extends the threat model and security advice given in RFCs 6749, 6750, and …
-
rfc-editor.orghttps://www.rfc-editor.org › info › rfc9276RFC 9276: Guidance for NSEC3 Parameter Settings | RFC Editor
More about rfc-editor.org
Aug 11, 2022. View as: Plain Text , Compact HTML , PDF RFC 9276 : BCP 236 : Guidance for NSEC3 Parameter Settings DNSSEC August 2022. W. Hardaker , V. Dukhovni Best Current Practice 18 subscribed Added to 2 Sets …
-
rfc-editor.orghttps://www.rfc-editor.org › subjects › j-pakeRFCs about J-PAKE | RFC Editor
More about rfc-editor.org
… remote parties over an insecure network solely based on a shared password, without requiring a Public Key Infrastructure (PKI) or any trusted third party. Abstract This document specifies a Password-Authenticated Key …
-
rfc-editor.orghttps://www.rfc-editor.org › info › rfc9906RFC 9906: Deprecate Usage of ECC-GOST within DNSSEC | RFC Editor
More about rfc-editor.org
Nov 30, 2025. … 94 DS records as insecure. If no other DS records of accepted cryptographic algorithms are available, the DNS records below the delegation point MUST be treated as insecure. ¶ The GOST R 34.10 …
-
rfc-editor.orghttps://www.rfc-editor.org › info › rfc6797RFC 6797: HTTP Strict Transport Security (HSTS) | RFC Editor
More about rfc-editor.org
Nov 20, 2012. View as: Plain Text , Compact HTML RFC 6797 : HTTP Strict Transport Security (HSTS) IDN TLS HTTP HSTS November 2012. J. Hodges , C. Jackson , A. Barth Proposed Standard 25 subscribed Added to 5 …
-
rfc-editor.orghttps://www.rfc-editor.org › info › rfc9905RFC 9905: Deprecating the Use of SHA-1 in DNSSEC Signature Algorithms | RFC Editor
More about rfc-editor.org
Nov 30, 2025. … SHA1 DS records as insecure. If no other DS records of accepted cryptographic algorithms are available, the DNS records below the delegation point MUST be treated as insecure. ¶ The RSASHA1 [ RFC4034 ] and …
Search for “Insecure site:rfc-editor.org” on Google, or add !ddg, !w and other shortcuts to any search.