Protocols
Saved & recent

Protocol greasing

Also called: GREASE, Generate Random Extensions And Sustain Extensibility

Protocol greasing deliberately exercises extension points so implementations keep accepting unfamiliar but permitted values. Without it, deployed software can accidentally depend on seeing only today’s known options, making future additions fail. TLS GREASE reserves values that implementations can include in appropriate offers to expose this kind of accidental rigidity.

For example, a client can offer a reserved GREASE cipher-suite value alongside real supported suites. A compatible server ignores that unknown choice and selects an actual shared suite; it must not negotiate the GREASE value itself. This tests an existing extensibility rule using well-formed messages. It is not permission to ignore malformed data or unknown values in fields whose rules require rejection.

Read first
Protocol extensibility
Related
TLS, Protocol extensibility, Protocol conformance
Further reading
IETF — RFC 8701, TLS GREASE
TLS client TLS server 0x0A0A TLS_AES_128_GCM_SHA256 reserved GREASE 0x0A0A reserved option skipped TLS_AES_128_GCM_SHA256 mutually supported selection room for future extensions
A GREASE offer keeps the unknown-option path exercised while the server selects a real mutually supported choice.

View in the full Protocols collection