mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-02 22:46:30 +02:00
dirmngr: New option --compatibility-flags.
* dirmngr/dirmngr.c (oCompatibilityFlags): NEw. (opts): Add option --compatibility-flags. (compatibility_flags): New. (parse_rereadable_options): Parse them.
This commit is contained in:
parent
3bab25d7d5
commit
bf04b07327
3 changed files with 43 additions and 0 deletions
|
@ -154,6 +154,9 @@ struct
|
|||
current after nextUpdate. */
|
||||
|
||||
strlist_t keyserver; /* List of default keyservers. */
|
||||
|
||||
/* Compatibility flags (COMPAT_FLAG_xxxx). */
|
||||
unsigned int compat_flags;
|
||||
} opt;
|
||||
|
||||
|
||||
|
@ -182,6 +185,18 @@ struct
|
|||
#define DBG_EXTPROG (opt.debug & DBG_EXTPROG_VALUE)
|
||||
#define DBG_KEEPTMP (opt.debug & DBG_KEEPTMP_VALUE)
|
||||
|
||||
/* Compatibility flags */
|
||||
|
||||
/* Since version 2.2.12 dirmngr restricted HTTP redirection in an
|
||||
* attempt to mitigate certain CSRF attacks. It turned out that this
|
||||
* breaks too many WKD deployments and that the attack scenario is not
|
||||
* due to gnupg's redirecting but due to insecure configured systems.
|
||||
* Thus from 2.4.3 on we disable this restriction but allow to use the
|
||||
* old behaviour by using this compatibility flag. For details see
|
||||
* https://dev.gnupg.org/T6477. */
|
||||
#define COMPAT_RESTRICT_HTTP_REDIR 1
|
||||
|
||||
|
||||
/* A simple list of certificate references. FIXME: Better use
|
||||
certlist_t also for references (Store NULL at .cert) */
|
||||
struct cert_ref_s
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue