Checklist

• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

doc

Description of change

The default encoding for crypto methods was changed in v6.0.0, with v4.x keeping a default of binary.

Ref: #5500
Fixes: #7712

LGTM. Perhaps the documentation could be explicit about the fact that the default encoding changed in v6?

Aside: 'enforced' is a bit of an odd choice of words.

I’ve updated with “implied” substituted where “enforced” is currently being used. And +1 to being explicit about the change in v6, but that should probably go into a different PR against master.

@addaleax is this important enough to be rolled into v4.5.0 or could it wait for the next patch release?

@thealphanerd uff… doesn’t really matter? It can wait, but it’s a only a correction in the docs.

The default encoding for crypto methods was changed in v6.0.0,
with v4.x keeping a default of `binary`.

Ref: #5500
Fixes: #7712
PR-URL: #7799
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: James M Snell <jasnell@gmail.com>