#1142539 unbound: Doubles the traffic to the root zone system when serve stale is enabled

Package:
unbound
Source:
unbound
Description:
validating, recursive, caching DNS resolver
Submitter:
Ondřej Surý
Date:
2026-09-21 18:49:03 UTC
Severity:
normal
#1142539#5
Date:
2026-07-21 13:24:15 UTC
From:
To:
Dear Maintainer,

I've been told by several root nameservers that version of unbound
as shipped by Debian has a serious flaw that causes unbound to double
the traffic to the root zone system endangering the whole stability
of the DNS system (the RZ operators could still cope with this, but
doubling the traffic is quite horrible).

There has been large operator that upgraded to Debian Trixie and
enabled serve-stale and this has caused several eyebrows to raise,
and people coming to me (since they know I am DD) asking if I can
help.

NLNetLabs had been notified, but since this is already fixed in
the upstream packages, this needs to be expeditely fixed in Debian
as this can cause instability in the DNS ecosystem.

Please look into this as soon as possible, or ping me if you want
me to NMU unbound via security-team.  I am notifying the security
team as well.

Thanks,
Ondrej

- -- System Information:
Debian Release: 13.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates'), (500, 'stable'), (50, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.94+deb13-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages unbound depends on:
ii  adduser                     3.152
ii  init-system-helpers         1.69~deb13u1
ii  libc6                       2.41-12+deb13u3
ii  libevent-2.1-7t64           2.1.12-stable-10+b1
ii  libhiredis1.1.0             1.2.0-6+b3
ii  libnghttp2-14               1.64.0-1.1+deb13u1
ii  libprotobuf-c1              1.5.1-1
ii  libpython3.13               3.13.5-2+deb13u3
pn  libpython3.14               <none>
ii  libssl3t64                  3.5.6-1~deb13u2
ii  libsystemd0                 257.13-1~deb13u1
ii  systemd [systemd-tmpfiles]  257.13-1~deb13u1

Versions of packages unbound recommends:
ii  dns-root-data  2025080400~deb13u1

Versions of packages unbound suggests:
pn  apparmor  <none>
ii  openssl   3.5.6-1~deb13u2
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmpfcv9fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcLegxAAi1YVu97jM6GQvqzoaPSC/r80WBcsGtnOd8Tyd89t8HOImo+nIoPf5Udy
TlN3bu324oh3jm3VYfkte/pWGP55UwHR47Lez4eHA32YXbV2JBZz7Xgc1MBs+WM5
G6smtsaiCpxDLXVCt4QLFmNsQGfPzDz2WNRCo/8FZjXbHtP7EMReDknRXL+JR4Gh
OPcRodwYzuDGRwwWeIPI1le/jtpjYjRk8CEC59nw2WSLgmwLs8yqF6HhPmWQlSp2
PKpLh79BB3AXPl1fnraq6A5GYenm1UKamuEO/AQCaXCm3HGWAJOu6+T+tykXTHsF
K2ApIBax/Ihfi728/evdNVeWH+iiNG5zntIKgDy8IBC5p8TD8KIaSM9PW5pff2Br
Ii1XO3OmOv3QJz10cODqZu2+9fQ5e4fLgzDK14NYGAyoyQBe/gS75wXFLgFRLE9d
UIHSPCaDsLSz+eTpSdX7M9uF6oMUx9pCImUix/OkquvM0VbRuAhoSeTS+nEjtV9A
NQklG1tp48TK+GcrU5P/OP9ijAnAXj3Bp0ZpZqMzehz+9Sov+oCooxIxdh0lnqFJ
kI48f0+D+VgPlmvoX8nO456LxzP1LZPZC4iNQOwI7TLX6M78FcM6bw+RMn4+Hnqi
XB+/bBNk8VmLVt26dF3hCbSjzCH04yhkOHOgeZii+SjC2r73d3Y=
=7rBu
-----END PGP SIGNATURE-----

#1142539#10
Date:
2026-07-21 13:53:00 UTC
From:
To:
Hi,
a security issue in unbound), so an update via a stable-update (with a
SUA advisory) seems more appropriate.

See: https://wiki.debian.org/StableUpdates
https://lists.debian.org/debian-stable-announce/

Regards,
Salvatore

#1142539#15
Date:
2026-07-21 14:46:46 UTC
From:
To:
So what is the upstream bugfix?

Thanks,

/mjt

#1142539#20
Date:
2026-07-21 15:56:51 UTC
From:
To:
That’s probably fine as well, but my reasoning is that such issue is a borderline DDoS on the root zone system.

At least three different root server operators came to me with this.

Ondřej
--
Ondřej Surý (He/Him)

A gentle nudge is always appreciated if I take a little longer to reply.

#1142539#25
Date:
2026-07-21 16:00:07 UTC
From:
To:
Hi Michael,

I believe it is this one: https://github.com/NLnetLabs/unbound/issues/1174
and the fix is: https://github.com/NLnetLabs/unbound/commit/fff9f62a1ec008185868a369207b0d56ffb7dcb3
(Just confirmed by Yorgos.)

There will be security release for Unbound tomorrow, so I think bundling
this fix with the security update would make sense and make DNS people
happy.

Ondrej
--
Ondřej Surý (He/Him)
ondrej@sury.org

A gentle nudge is always appreciated if I take a little longer to reply.

#1142539#30
Date:
2026-07-21 17:29:38 UTC
From:
To:
Note this commit is based on https://github.com/NLnetLabs/unbound/commit/d5e91d181
(at least contextually - it uses extra parameter is_valrec to iter_dns_store(),
added by d5e91d181.

With so much quite sensitive changes for such a fragile area, I'm not confident
to just cherry-pick these two commits (without the Changelog parts) and hope the
whole thing will work correctly.

Thanks,

/mjt

#1142539#35
Date:
2026-07-22 07:10:29 UTC
From:
To:
The debdiff is attached.  But I haven't verified if the result fixes the issue.
At the very least, regular operations of unbond seems to be unaffected by the
two patches, the thing continue to work.

As stated by Salvatore already, this is not a security material for debian,
but if we're to release a real security update, this change can be squashed
into that one.

Thanks,

/mjt

#1142539#40
Date:
2026-07-23 07:47:35 UTC
From:
To:
Version: 1.23.0-1

This is fixed in upstream release 1.23.0, so sid & testing is
unaffected by this.

I'm also not in agreement with the bug severity, but that does
not really matter here.

After the subsequent discussion, verifying locally and confirmation
with the upstream, I'm confident enough with the changes I collected
from the upstream commits to fix this issue, it should be ok to
update unbound in trixie now.

However, after the yesterdays upstream release of unbound, 1.25.2,
and after I tried picking up fixes in there for the trixie version,
I can conclude this is not going to work - at least not the way I
did it before.  It looks like this time, we'll have to update
unbound in trixie to the last upstream version (1.25.2), instead
of patching the vulnerabilities in 1.22 version.

An interesting note - some security fixes require previous fixes
which either needs to be back-ported to previous version - and quite
some of them are obvious bug fixes, and some requires even more prior
fixes too! - or the subsequent changes should be edited, including
re-thinking and re-evaluating the logic behind them - to work in older
context.

I did quite some work trying to adopt previous batch of security
fixes in unbound for the trixie version - and each time tried to
decide what to do, - to pick up another prior fix, or to edit the
fix being applied.  I tend to do the former, but only if the chain
of pick-ups isn't large.  Now with the new set, some prior fixes
which I missed previously, should finally be picked up too, and
the already applied changes re-done in context of new pick-ups.

And all this becomes unique to debian, with resulting version being
our own, with no way if the final logic actually works or not - we
risk to have other hidden vulnerabilities and bugs because of
unknown and unique combination of (modified) patches collected.

I'm now at patch 5 out of 24 from the Jul-2026 batch (1.25.2),
and I think I'll give up here.  Either we update unbound to
1.25.2 in trixie, or we declare it's not supported in there,
and recommend to install it from bpo13 (which I'll publish with
pleasure).

Speaking of the API/ABI stability - unlike some other software,
here with unbond it should be entirely okay to update it with
no risk of breaking some reverse dependency.

Thanks,

/mjt

#1142539#49
Date:
2026-09-21 18:47:07 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
unbound, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1142539@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Tokarev <mjt@tls.msk.ru> (supplier of updated unbound package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 17 Sep 2026 11:55:59 +0300
Source: unbound
Architecture: source
Version: 1.26.1-0+deb13u1
Distribution: trixie-security
Urgency: medium
Maintainer: unbound packagers <unbound@packages.debian.org>
Changed-By: Michael Tokarev <mjt@tls.msk.ru>
Closes: 1096189 1142539
Changes:
 unbound (1.26.1-0+deb13u1) trixie-security; urgency=medium
 .
   * New upstream release fixing numerous security and other issues and contains
     some enhancements.
 .
     Traditionally in Debian, bugs in stable versions are fixed by providing
     a back-port of a fix from later upstream version to the version in Debian
     stable.  With unbound, fixes in subsequent versions can not be applied
     directly to the version in Debian stable, as there were multiple other code
     changes in these areas.  Many of these changes fixes other issues (security
     or not).  Some changes are in areas with complex logic, hence requires
     creat care when back-porting to older releases.  And the result of such
     back-porting becomes unique and rather unpredictable.  So instead of trying
     to provide fixes for older version in Debian stable, we decided to provide
     current upstream version of unbound, - the same as currently available in
     Debian Sid.  The packaging is made very similar too.
 .
     Recent security fixes:
 .
     o CVE-2026-81642 - severity: CRITICAL
       Heap buffer overflow and possible Remote Code Execution
       when digesting DNSKEY
     o CVE-2026-81634 - severity: HIGH
       Possible heap buffer overflow during DNSSEC canonicalization
     o CVE-2026-82717 - severity: HIGH
       CNAME synthesis could lead to heap corruption
     o CVE-2026-77955 - severity: MEDIUM
       Possible ZONEMD verification bypass window
     o CVE-2026-78227 - severity: MEDIUM
       Use-after-free in DoQ stream output buffer on reset re-transmission
     o CVE-2026-80225 - severity: MEDIUM
       Possible degradation of service from continuous queries
       on the same TCP/DoT connection
     o CVE-2026-82720 - severity: MEDIUM
       Use-after-free in DoH stream cleanup code path
     o CVE-2026-85501 - severity: MEDIUM
       Retrap: Novel Vulnerabilities to launch Algorithmic Complexity Attacks
       on DNSSEC
     o CVE-2026-77860 - severity: LOW
       'serve-expired' can bypass Unbound 'wait-limit'
     o CVE-2026-32665 - severity: HIGH
       Remote DNS-over-QUIC denial of service due to `quic-size` budget bypass
     o CVE-2026-40691 - severity: HIGH
       Packet of death for DNSCrypt over TCP
     o CVE-2026-44690 - severity: HIGH
       Cross-zone wildcard cache poisoning via RRSIG.labels manipulation
     o CVE-2026-55973 - severity: HIGH
       'dns-error-reporting: yes' leads to stack buffer overflow
     o CVE-2026-14586 - severity: MEDIUM
       Assertion in libngtcp2 when under pressure in high concurrency
       DNS-over-QUIC environments
     o CVE-2026-44621 - severity: MEDIUM
       Libunbound applications configured with 'unwanted-reply-threshold'
       could eventually be abruptly terminated
     o CVE-2026-50045 - severity: MEDIUM
       'max-global-quota' reset by DNSSEC validation restarts
     o CVE-2026-50046 - severity: MEDIUM
       Possible heap use-after-free in an error path when
       a DoT forwarded query is jostled out
     o CVE-2026-50243 - severity: MEDIUM
       response-ip/rpz can rewrite BOGUS answers instead of returning SERVFAIL
     o CVE-2026-50248 - severity: MEDIUM
       BOGUS configured primary hostname accepted for XFR in auth/rpz zones
     o CVE-2026-50251 - severity: MEDIUM
       Attacker supplied 0.0.0.0/:: glue triggers defensive full-cache flush
     o CVE-2026-50252 - severity: MEDIUM
       Possible cache poisoning attack by mapping source port population
       per thread
     o CVE-2026-52863 - severity: MEDIUM
       Memory corruption could lead to crash and denial of service
     o CVE-2026-55717 - severity: MEDIUM
       'serve-expired-client-timeout' and 'response-ip' CNAME redirect
       could lead to a crash
     o CVE-2026-55990 - severity: MEDIUM
       Packet of death for a DNSCrypt misconfigured Unbound
     o CVE-2026-55991 - severity: MEDIUM
       Remote DNS-over-QUIC (DoQ) flow-control assertion failure in libngtcp2
     o CVE-2026-56416 - severity: MEDIUM
       Possible heap buffer overflow when validator canonicalizes RDATA
       that contains domain name
     o CVE-2026-56444 - severity: MEDIUM
       Degradation of resolution service when 'discard-timeout' and
       'serve-expired-client-timeout' are combined in unusual configuration
     o CVE-2026-41637 - severity: LOW
       Degradation of resolution service from improperly accounted
       client-terminated DNS-over-QUIC queries
     o CVE-2026-42955 - severity: LOW
       Extra fix for CVE-2026-40622 to also clamp the TTL of A/AAAA records
       disallowing a one-time 'ghost domain' delegation renewal via glue records
     o CVE-2026-44687 - severity: LOW
       Off-by-one error in 'harden-below-nxdomain' logic can shadow
       a stub/forward zone by a legitimate parent's NXDOMAIN
     o CVE-2026-46582 - severity: LOW
       A wildcard replay, as another piece of data, triggers poisoning
       in the serve expired reply path
     o CVE-2026-54478 - severity: LOW
       DNS Cookie bypass when combined with proxy-protocol use
     o CVE-2026-55708 - severity: LOW
       Privacy/configuration issue when adding local data in views
       through 'unbound-control'
 .
     Other notable user-visible changes and fixes.  For complete list, please
     see /usr/share/doc/unbound/changelog.gz
 .
     o ICANN Bundle Update: Refreshed icannbundle.pem certificates in
       unbound-anchor to include public keys valid for 2009–2029 and 2025–2045
     o Transfer Limits: Added max-transfer-size and max-transfer-time directives
       to limit authorization zone (auth-zone) and RPZ transfer sizes and times
       to harden against unbounded transfers.
     o New Zone Types: Introduced block_aaaa static zone type to suppress AAAA
       queries, plus block_a_wdata and block_aaaa_wdata to support custom local
       data fallback.
     o Management Improvements: Overloaded local_data_remove
       to allow the removal of precise records.
     o Fix for the Jiggle Attack. The server is fixed to answer with errors
       for error cases, and does not stay silent.  In addition, the error
       replies do not contain parts of the incoming query.  This is more
       conformant, stops reflection and stops it as a covert channel.
     o Fix EDNS extended RCODE reflection. This fixes that the server does not
       echo extended rcode values after class chaos queries.
     o Fix for iterator RCODE handling of YXDOMAIN.  This fixes that the server
       only accepts YXDOMAIN answers that contain a DNAME record.  This stops
       bad answers, and checks that the authoritative server gives correct
       replies.
     o Fix for missing bounds check for decompressing dnames for downloaded
       authority zones.  This fixes that the server could end up with malformed
       zone content after receiving truncated packet contents from an AXFR.
       In addition, the domain names in the SOA rdata are checked before the
       authority code picks up the zone serial.
     o Fix that upstream TLS connections are not reused as TLS connections for
       a different name, at the same IP.  This checks that the tls name is
       correct when reusing the upstream connections.
     o Fix that signatures are not allowed with revoked dnskeys.
     o Fix that a DNAME with an unsigned CNAME is checked for the correct match.
       This stops that for certain zone configurations an unchecked unsigned
       CNAME could get secure status.
     o Fix handling of wildcard CNAMEs in the chain of trust.  An improper
       wildcard in the chain of trust would send the retries to the wrong
       upstream.  Also it could label the step in the chain of trust as secure,
       when it was not.
     o Introduce new 'tls-protocols' configuration option that specifies which
       of the supported TLS protocols will be used.
     o Fix RFC7766 compliance when client sends EOF over TCP.
       It stops pending replies and closes.
     o Fix to shorten RRSIG count in scrubber, this protects against an overly
       large number of RRSIGs.  It can be configured with `iter-scrub-rrsig: 8`,
       it has default 8.
     o Fix for EDNS client subnet so that it does not store SERVFAIL in the
       global cache after a failed lookup, such as timeouts.  A failure entry is
       stored in the subnet cache, for the query name, for a couple of seconds.
       Queries can continue to use the subnet cache during that time.
     o Fix to allow the control-interface config to use ip@port notation.
     o Fix to check for invalid http content length and chunk size, and to check
       the RR rdata field lengths when decompressing and inserting RRs from
       an authority zone transfer.  This stops large memory use and heap
       buffer-overflow read errors.
     o Fix to ignore out-of-zone DNAME records for CNAME synthesis.
       Fix so that a reload checks if the files have changed, and if so, reload
       the contexts.  Also for DoH, DoQ and outgoing DoT.
     o Apply cache TTL policy to DNAME and synthesized CNAME on wire path.
     o Fix for DNS Rebinding Bypass via SVCB/HTTPS Records in Unbound.
     o Allow synthesized DNAME TTL=0 to be served from cache within grace
       period.  The responses are served from cache within a 1-second grace
       period.  Reduces recursion when authoritative servers return DNAME with
       TTL=0 (RFC 2308).  Response still returns TTL=0 to clients.
     o On Linux systems log the system-wide unique thread ID instead of
       Unbound's internal thread counter.
     o Introduce the 'log-thread-id' configuration option to manage logging the
       system-wide Linux thread ID for easier debugging with system tools.
     o Mesh reply counters.  This adds statistics num.queries.replyaddr_limit
       and requestlist.current.replies.
     o Add extra statistic to track the number of signature validation
       operations.  Adds 'num.valops' to extended statistics.
     o Fix for cname chain length with qtype ANY and qname minimisation.
     o Change default for so-sndbuf to 4m, to mitigate a cross-layer issue where
       the UDP socket send buffers are exhausted waiting for ARP/NDP resolution.
     o Increase default to `num-queries-per-thread: 2048`, when unbound is
       compiled with libevent.  It makes saturation of the task queue more
       resource intensive and less practical.
     o DNS Error Reporting (RFC 9567).  Introduces new configuration option
       'dns-error-reporting' and new statistics for 'num.dns_error_reports'.
     o Redis read-only replica support.  Introduces new 'redis-replica-*'
       options for the Redis cache backend.
     o Exempt loopback addresses from wait-limit.
     o Fix wait-limit-netblock and wait-limit-cookie-netblock config parse
       to allow two arguments.
     o Fast Reload.  The unbound-control fast_reload is added.  It reads
       changed config in a thread, then only briefly pauses the service threads,
       that keep running.  DNS service is only interrupted briefly.
     o Make the default value of module-config "validator iterator" regardless
       of compilation options.  --enable-subnet would implicitly change the
       value to enable the subnetcache module by default in the past.
     o Add unbound members group access to control key.
     o Add resolver.arpa and service.arpa to the default locally served zones.
     o Use TCP_NODELAY on TLS sockets to speed up the TLS handshake.
     o Serve expired cache update fixes.  Fixes a regression bug with
       serve-expired that appeared in 1.22.0 and would not allow the iterator
       to update the cache with not-yet-validated entries resulting in increased
       outgoing traffic.  Closes: #1142539
     o The default value of serve-expired-ttl is set to 86400 (1 day)
       as suggested by RFC8767.
     o Increase the default of max-global-quota to 200 from 128 after
       operational feedback.  Still keeping the possible amplification factor
       (CAMP related issues) in the hundreds.
     o Fix for the serve expired DNSSEC information fix, it would not allow
       current delegation information be updated in cache.  The fix allows
       current delegation and validation recursion information to be updated,
       but as a consequence no longer has certain expired information around
       for later dnssec valid expired responses.
     o Statistics for discard-timeout and wait-limit.
 .
   * Other packaging changes:
    - d/rules,d/libunbound-dev.install: drop static library and deps
      (Closes: #1096189)
    - unbound-helper: do not update resolvconf if it is systemd-resolved
    - d/unbound.service: set empty DAEMON_OPTS= to avoid warning from systemd
    - d/upstream/signing-key.asc: update with the new upstream key
    - d/unbound.conf.d/remote-control.conf: fix typo
Checksums-Sha1:
 6318f69bbf1a4c21f7acd31438b97c7989361e67 3201 unbound_1.26.1-0+deb13u1.dsc
 e4554010d4349038c7de117779b65a4d8b35a663 6948585 unbound_1.26.1.orig.tar.gz
 daabbe2a34dfe39a1e0b86cd3a6671e3da37c4e3 659 unbound_1.26.1.orig.tar.gz.asc
 68bbbcab56f0f9f084a4d1ca265b815da35b779c 32356 unbound_1.26.1-0+deb13u1.debian.tar.xz
 a33e2fbc1f3cad0732fbe7cd6fa16077e59ba1eb 5867 unbound_1.26.1-0+deb13u1_source.buildinfo
Checksums-Sha256:
 5cfa6c981408a173490f851011f7151828a6626679ef78b1e4767ec55290e5dc 3201 unbound_1.26.1-0+deb13u1.dsc
 35a6dc0e425a9282c3426d9a3043144011bf0534aed4b73ab62c52aee0af1503 6948585 unbound_1.26.1.orig.tar.gz
 c52227c2a6918f991443c72709313fcd8530c41ea61268dbe820278a1c60a996 659 unbound_1.26.1.orig.tar.gz.asc
 22430ce4c5ab232b9530b1f7a0a21126a4ae745dfea7860c8a6b39c6851a86e4 32356 unbound_1.26.1-0+deb13u1.debian.tar.xz
 dcb33a24d6d2c272801c8948872a7fd5ff9197dddd7cc4be2c6c6df50b0671e3 5867 unbound_1.26.1-0+deb13u1_source.buildinfo
Files:
 8f35b0dc5a8b6324840954046b376a65 3201 net optional unbound_1.26.1-0+deb13u1.dsc
 249968d910bcf13232fbecef8db17124 6948585 net optional unbound_1.26.1.orig.tar.gz
 8d8aa9bfcadded4e7d2ac0e8c67be654 659 net optional unbound_1.26.1.orig.tar.gz.asc
 e36ec6e3be1f2e40ff2a4d5bbb4ea34b 32356 net optional unbound_1.26.1-0+deb13u1.debian.tar.xz
 86e78ca6d78d79997e5b8243756024bb 5867 net optional unbound_1.26.1-0+deb13u1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZKoqtTHVaQM2a/75gqpKJDselHgFAmqtYY0ACgkQgqpKJDse
lHiZCg/+JnFyX2TVhxll4OL7dxKmVklzR95k+UYSSKUvOWbvHi4ERLV/s96Oxacv
jgD4l7SZBdSM0Q1pZHDuJq8lc6h/r2BpToA5B4qyO3vAEQiEK8b8TJGnvqiBqr89
LX5ddPldKtdVP1gKm+lXohx5gcpfp7Xz0lCW2lF1zVoX/wIzJqmt5+FPFTkYaH0l
RYlevTcyVukXOvFZa1C4nmuaUUELChy07RnntNlg04kLIifqCZU/3KwiUAi0rabo
96orSMcJzKyX290NhnujWO2LGLqe55YrSrYIg+rYEtFaa9tSlyEb1riwbz8+vzFl
xncuPYPskmNS/ZP67ZXUHqsillwWzdBJry2qXJ+Nia0TSR9N3mMnmfiqLLCWr+6O
/6nyHD6uIm6/TupUwkhY+0vuxde4XEZiDbQu8pv3+Z4okklDJHNu6I419PV3C8qF
mCY5WuxrYbzv35zuOrxx1FQuc83E3ekxDpw8llJSMdia7lS/Mb9qbS5Mvp+Hgwgc
mSGTtsjNe4kDKNkuu0sKobIZVURpjqKkSHD+L+UOMW+SLqKhz/7IDwwAGwdc9G+3
xrajVqrfhoqPiexB6qh4DwlDMBzDxymaG3RI9AUSemuATrkqRgnS38meSQw3hqhB
CI5H+gFZxWDWxjBDDWXJcc9XfbAHTxeCxzS2DUQG+Dxvju4j9aA=
=GeVk
-----END PGP SIGNATURE-----