-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 11 Aug 2026 23:32:38 +0200 Source: postgresql-17 Binary: libecpg-compat3 libecpg-compat3-dbgsym libecpg-dev libecpg-dev-dbgsym libecpg6 libecpg6-dbgsym libpgtypes3 libpgtypes3-dbgsym libpq-dev libpq5 libpq5-dbgsym postgresql-17 postgresql-17-dbgsym postgresql-client-17 postgresql-client-17-dbgsym postgresql-plperl-17 postgresql-plperl-17-dbgsym postgresql-plpython3-17 postgresql-plpython3-17-dbgsym postgresql-pltcl-17 postgresql-pltcl-17-dbgsym postgresql-server-dev-17 postgresql-server-dev-17-dbgsym Architecture: armel Version: 17.11-0+deb13u1 Distribution: trixie-security Urgency: medium Maintainer: armel Build Daemon (arm-ubc-01) Changed-By: Christoph Berg Description: libecpg-compat3 - older version of run-time library for ECPG programs libecpg-dev - development files for ECPG (Embedded PostgreSQL for C) libecpg6 - run-time library for ECPG programs libpgtypes3 - shared library libpgtypes for PostgreSQL 17 libpq-dev - header files for libpq5 (PostgreSQL library) libpq5 - PostgreSQL C client library postgresql-17 - The World's Most Advanced Open Source Relational Database postgresql-client-17 - front-end programs for PostgreSQL 17 postgresql-plperl-17 - PL/Perl procedural language for PostgreSQL 17 postgresql-plpython3-17 - PL/Python 3 procedural language for PostgreSQL 17 postgresql-pltcl-17 - PL/Tcl procedural language for PostgreSQL 17 postgresql-server-dev-17 - development files for PostgreSQL 17 server-side programming Changes: postgresql-17 (17.11-0+deb13u1) trixie-security; urgency=medium . * New upstream version 17.11. . + Restrict logical decoding output plugins to the set specified by a new server parameter `output_plugin_libraries` (Jacob Champion) . Previously, a replication user could select any loadable library for logical decoding, allowing exploits of various sorts. To allow locking this down without breaking setups that worked before, introduce a whitelist of allowed output plugins. . By default, only the output plugins shipped as part of PostgreSQL (`pgoutput` and `test_decoding`) are included in `output_plugin_libraries`. Installations that rely on other output plugins must add them after updating the server, for example . output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder' . Additionally, pg_upgrade --check will fail if the `output_plugin_libraries` parameter on the new cluster does not permit the plugins of logical replication slots on the old cluster, when migrating from versions 17 and later. Make necessary additions to the new cluster's setting before performing pg_upgrade. . The PostgreSQL Project thanks Vladimir Tokarev and Yu Kunpeng for reporting this problem. (CVE-2026-6471) . + Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers (Daniel Gustafsson) . Previously, if OpenSSL rejected the requested cipher (for example, because it is running in FIPS mode, or the legacy provider hasn't been loaded), pgcrypto failed to notice the failure and simply XOR'd the non-encrypted block with the plaintext, rendering the "encryption" trivially breakable. This will typically occur with deprecated or non-FIPS cipher algorithms (cipher-algo=blowfish/bf, twofish, cast5, or 3des). . By default, pgcrypto will now fail to decrypt any messages that were affected in this way. To allow retrieval of such data, a new option `ignore-cipher-failure` has been added to pgp_pub_decrypt() and pgp_sym_decrypt(). Setting `ignore-cipher-failure=1` will restore their previous behavior, allowing the faulty encryption wrapper to be stripped off: . pgp_sym_decrypt(encrypted_column, any key, 'ignore-cipher-failure=1') . Once the affected messages are identified and stripped of their wrappers, they can then be re-encrypted with a modern algorithm. It is important however that the behavior of OpenSSL be the same as it was when the faulty messages were created: if the set of unsupported algorithms is not the same, this approach will not work. See the documentation for `ignore-cipher-failure`. . The PostgreSQL Project thanks Shishir Sharma for reporting this problem. (CVE-2026-14663) . + Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending `PGRES_COPY_IN` (Tom Lane) . Previously, if a `COPY` command failed at startup (for instance, because the target table doesn't exist) psql would not realize that and would proceed to read the following in-line data as SQL commands. In the best case that's wrong and in the worst case it's a SQL-injection hazard. Teach psql to recognize syntactically-valid COPY ... FROM STDIN commands and to skip data on its own authority if the server doesn't respond with `PGRES_COPY_IN`. . While this fix is unlikely to affect any production SQL scripts, test scripts might intentionally exercise failing COPY ... FROM STDIN commands. Those will need to gain a `\.` data terminator line after each such command. . The PostgreSQL Project thanks Alexander Lakhin for reporting this problem. (CVE-2026-6464) . + Cross-check the output row type of a portal running EXECUTE or FETCH (Robert Haas) . EXECUTE and FETCH use two portals: an outer one for the statement itself, and an inner one running the query being executed on its behalf. It was previously possible to make the declared row types of the two portals diverge, leading to server memory disclosure and arbitrary code execution. . The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) and Peter Geoghegan for reporting this problem. (CVE-2026-16239) . + Fix buffer overrun with long time zone abbreviation in to_char() (Tom Lane) . This can easily crash the server, and exploits leading to arbitrary code execution have been reported. . The PostgreSQL Project thanks Hcamael, Amjad Shahzad, Tan Zhen of AntAISecurityLab, Tomer Fichman, Zheng Yu, Amy Burnett (OpenAI Codex Security), Rick de Jager, Heewon Song, Sylvie Mayer, Aleksander Alekseev, and Hillai Ben Sasson for reporting this problem. (CVE-2026-14669) . + Fix buffer overrun in regexp match/split functions (Masahiko Sawada) . If passed invalidly-encoded data, these functions could write past the end of their conversion buffer. . The PostgreSQL Project thanks Francesco Verardi for reporting this problem. (CVE-2026-14664) . + Harden the ascii() function against invalid input (Michael Paquier) . By supplying invalidly-encoded input, this function could be coaxed to read and return a few bytes of data that it shouldn't. In assert-enabled builds, its assertions could be triggered too. . The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-18024) . + Fix multirange type handling in pg_restore_attribute_stats() (OpenAI Security Research Team) . pg_restore_attribute_stats() treated multirange types just like their underlying range type. This works correctly for the bounds histogram, but it was wrong for all the other statistics kinds. . The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-16238) . + Make scalarineqsel() check that a constant it expects to be of type tid actually is (Tom Lane) . This expectation will hold for all the built-in operators that use this estimator, but a maliciously-constructed operator could violate it, leading to a crash or server memory disclosure. . The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14668) . + Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length) (Tom Lane) . The documented limits were not enforced in all code paths. . The PostgreSQL Project thanks Yuhang Wu, Zhenpeng Lin, Zheng Yu, and Hcamael for reporting these problems. (CVE-2026-14662) . + Fix various places that mistakenly assumed they would not have to deal with more than `FUNC_MAX_ARGS` function arguments (Tom Lane) . Notably, the server's actual limit on the number of arguments to an aggregate function is `FUNC_MAX_ARGS - 1`, but the parser failed to enforce that, creating hazards downstream. . The PostgreSQL Project thanks Zheng Yu, ylwangtju, and Masahiko Sawada for reporting these problems. (CVE-2026-14679) . + Reject calls from SQL to functions that take or return type internal (Tom Lane) . The existing defenses against doing this have been shown to be insufficient, so add more explicit checks. . The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-14680) . + Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE (Masahiko Sawada) . Previously, the role running ALTER TABLE gained ownership of such objects, but that seems inappropriate. . The PostgreSQL Project thanks Noah Misch for reporting this problem. (CVE-2026-6469) . + When deparsing an EXTRACT() function call, quote the field name if needed (Nathan Bossart) . The parser accepts any string literal as a field name in EXTRACT(), deferring validation to execution. If the call is stored and deparsed (for example during pg_dump), the string body was regurgitated verbatim, allowing SQL injection. . The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15741) . + Check for `USAGE` privilege on data types in places that formerly failed to check that (Nathan Bossart) . CREATE TYPE AS RANGE did not check, nor did ALTER TABLE OF, nor did commands that create stored expressions. These omissions allowed roles without `USAGE` privilege to nonetheless create objects depending on the type, possibly blocking the type's owner from changing the type later. . The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. (CVE-2026-6470) . + Invalidate role-dependent cached plans after role changes (Ilya Staroverov, Shinya Kato, Nathan Bossart) . Role membership, role attribute, and database ownership changes may impact the expected behavior of row-level security policies, but previously we'd continue to use cached plans that were made according to the old state of affairs. . The PostgreSQL Project thanks Ilya Staroverov and Shinya Kato for reporting this problem. (CVE-2026-14666) . + Reject GSSEncRequest after direct SSL connection (Michael Paquier) . After establishing a TLS-encrypted connection, the server would still accept a request for GSSAPI encryption. If that succeeded, the connection would proceed using TLS encryption, but it would look like a GSS connection to the pg_hba rules. Thus, a pg_hba policy intending to disallow TLS would not be enforced correctly. . The PostgreSQL Project thanks p4p3r for reporting this problem. (CVE-2026-14681) . + Make mock SCRAM authentication secrets more plausible (Nathan Bossart) . If a SCRAM login is attempted against a role that doesn't exist or doesn't have a SCRAM secret, we generate a mock secret and carry out the authentication handshake anyway, to avoid revealing these facts to an attacker. But the mock secret was made with a fixed iteration count, which in itself can be an observable response discrepancy. Use the configuration setting `scram_iterations` instead, to make the mock secret look more like the installation's real secrets. . The PostgreSQL Project thanks Radim Marek for reporting this problem. (CVE-2026-14672) . + Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server (Michael Paquier) . ecpg assumed without checking that any bytea value must begin with `\x`. A broken or malicious server might send a string shorter than 2 bytes, resulting in memory clobber in the application. . The PostgreSQL Project thanks ylwangtju for reporting this problem. (CVE-2026-16241) . + Do not do backquote expansion on the argument of psql's \unrestrict command (Nathan Bossart) . This oversight in the fix for CVE-2025-8714 allows a malicious server to inject shell commands into plain-text dump output that will be run at restore time on the machine running psql, the exact scenario that CVE-2025-8714 intended to prevent. . The PostgreSQL Project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem. (CVE-2026-18408) . + Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than `FUNC_MAX_ARGS` entries (Tom Lane) . Since there could be entries for both input and output arguments, it's feasible for this array's length to exceed `FUNC_MAX_ARGS` (which constrains only input arguments). Even if that were not so, pg_dump cannot assume that the server was built with the same value of `FUNC_MAX_ARGS` that it has. An overrun would lead to a memory clobber inside pg_dump. . The PostgreSQL Project thanks Masahiko Sawada for reporting this problem. (CVE-2026-19385) . + Harden PL/Perl against "tied" Perl arrays and hashes (Tom Lane) . A tied object that doesn't behave like a regular one could lead to memory overwrite, or to constructing a corrupt result array (which would likely cause problems later). . The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14670) . + Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl (Heikki Linnakangas) . This is the same type of problem as CVE-2026-6473, just in a different part of the code, and is fixed in the same way. . The PostgreSQL Project thanks the Tulya Project (Team Dhiutsa, Bitecope Technologies Private Ltd) for reporting this problem. (CVE-2026-14677) . + Ensure that contrib/amcheck functions restrict `search_path` before executing index expressions (Noah Misch) . Because amcheck will run such index expressions as the owner of their tables, a caller could potentially hijack `search_path`-dependent functions to run arbitrary code as the table owner. By default this is not a vulnerability because only superusers are allowed to call amcheck functions; but if that privilege was granted out, it created a larger hazard than the documentation suggests. . The PostgreSQL Project thanks Yuelin Wang and Jacob Brazeal for reporting this problem. (CVE-2026-14673) . + Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions (Nathan Bossart) . Passing large cost values to these functions could cause integer overflows, thereby producing nonsensical results, and even causing out-of-bounds writes in some cases. . The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15742) . + Fix buffer overrun in contrib/pg_stat_statements (Álvaro Herrera) . Query normalization didn't accurately account for the amount of space the normalized string would require. . The PostgreSQL Project thanks Sajeeb Lohani (with TrendAI Zero Day Initiative) and Yuelin Wang for reporting this problem. (CVE-2026-14676) . + Fix datatype error in contrib/pg_trgm's GiST picksplit function (Heikki Linnakangas) . This mistake resulted in reading past the end of the buffer, typically causing bad split decisions; but a crash could ensue if you're very unlucky. . The PostgreSQL Project thanks Mehmet D. Ince for reporting this problem. (CVE-2026-14678) . + Remove the plan cache in contrib/refint (Ayush Tiwari) . This caching behavior has several serious bugs, notably that check_foreign_key() embeds the new key values in its cascade-UPDATE queries, so a cached plan reuses the originally-needed values rather than the key values that should be used. The simplest solution is to remove it. . The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14671) . * Fix psql -c 'truncate/create table; copy from stdin'. Checksums-Sha1: 65afa64eaecb38b9c045f6de41b0427a2494b0ea 16652 libecpg-compat3-dbgsym_17.11-0+deb13u1_armel.deb c0c4aa6edcf27eae441d4d1abf14aed75e5b57cb 23564 libecpg-compat3_17.11-0+deb13u1_armel.deb 0c17c81bc808a70a0e925d1f7fbc04c29a7622ba 251252 libecpg-dev-dbgsym_17.11-0+deb13u1_armel.deb bba51fb73c2bb606e5d6921f65de979f844a4389 290408 libecpg-dev_17.11-0+deb13u1_armel.deb d016d346dfb8e496b10c77b2e4d20295add3a2dc 113140 libecpg6-dbgsym_17.11-0+deb13u1_armel.deb e3e14cd8a45874798909fddf7a9ba67f0b8260d6 63708 libecpg6_17.11-0+deb13u1_armel.deb 05d2b30cf3325bbc52c913eb60d494de6a934ff3 90772 libpgtypes3-dbgsym_17.11-0+deb13u1_armel.deb b972d88745f3d4fa6b08c83c12ed63ce9cd0f2bc 49780 libpgtypes3_17.11-0+deb13u1_armel.deb e80fa055feec338994396345c589b3fbc7e7d503 147124 libpq-dev_17.11-0+deb13u1_armel.deb e57317059b623ee2a64ce5124fe13b846746d558 293128 libpq5-dbgsym_17.11-0+deb13u1_armel.deb 4455e6bdd5f929dc9455eb305ec67f2cf84d0384 218784 libpq5_17.11-0+deb13u1_armel.deb 0efb9573261c44d8a7163d10cef36889d9ac4fa4 18866696 postgresql-17-dbgsym_17.11-0+deb13u1_armel.deb a2b0d2e4f18dc52f647888a79a58766b066fcd9a 17441 postgresql-17_17.11-0+deb13u1_armel-buildd.buildinfo 52729544e4585aa474eb06cbf45110e307b8d674 15999772 postgresql-17_17.11-0+deb13u1_armel.deb 4cafc9f5761f4108862a6c8fda41a7bbdfe11931 2826004 postgresql-client-17-dbgsym_17.11-0+deb13u1_armel.deb 6dfad20443c772734de6c66a517eb1114c7da476 1946844 postgresql-client-17_17.11-0+deb13u1_armel.deb 677e8c96d404bd5c1d2b57a8ee5ec1269f5b487d 197552 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_armel.deb d1b246cf8320bf8cb65c932dc7cee0938694cdfe 89968 postgresql-plperl-17_17.11-0+deb13u1_armel.deb c0b4c5d03cb62b7b0887522e67b5283e818d8a00 198684 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_armel.deb 792587a7094815d62e61c788b62e85d8052316c7 113764 postgresql-plpython3-17_17.11-0+deb13u1_armel.deb b3546f74e431a712c9c3dce41fbd6ce481648b29 82404 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_armel.deb d29610e28922a357fe7c559e352875890e8757c1 48016 postgresql-pltcl-17_17.11-0+deb13u1_armel.deb cae1a40fe06c53baf05f1e600600d336c1bee8b8 55932 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_armel.deb 66593dac5790981bec2312173642fbdc4994c4b0 1313028 postgresql-server-dev-17_17.11-0+deb13u1_armel.deb Checksums-Sha256: 84f27f04d030a73650b5d3f44519a3f2d0b77b517602e5b03ca20f2684000a33 16652 libecpg-compat3-dbgsym_17.11-0+deb13u1_armel.deb 136873b05aa1f141d4ae611e0501bc6215e6b2a22c17e14217d85c5975b54467 23564 libecpg-compat3_17.11-0+deb13u1_armel.deb 3fb646cc04de1e7d3fc4f4d6b12ba51b29fdf723de19acc6fae53ad46b063cff 251252 libecpg-dev-dbgsym_17.11-0+deb13u1_armel.deb 340ac2fb033cbe4f45b351bfdda5cd40fb21085c2d31d2aa8b4ae226a093b291 290408 libecpg-dev_17.11-0+deb13u1_armel.deb d26f619ca387b4d96abb78979f85ed686a4e21659ef8f28c16f8992d512f1007 113140 libecpg6-dbgsym_17.11-0+deb13u1_armel.deb 49a87feebadc6a637107b062bcbe3c1a382a66bb52c035c572a019224231f8fc 63708 libecpg6_17.11-0+deb13u1_armel.deb 08a273abb7d606d22578216d5ec17f5acd4290d9af4950bd5a4a677784e34eda 90772 libpgtypes3-dbgsym_17.11-0+deb13u1_armel.deb 72aa09c2b2700d9f84bcd73c320e18b5a9a4bb3ea70d5422f0adda12a4b2fb91 49780 libpgtypes3_17.11-0+deb13u1_armel.deb dada27ffa83802c6ef4c78416df3e0f7c22fa5ce74edd7365a596eea0ae0fc7a 147124 libpq-dev_17.11-0+deb13u1_armel.deb 83905790e20418dac3da1b39febe4bbbb1159b9ba337a2a9cff30bfc816708d6 293128 libpq5-dbgsym_17.11-0+deb13u1_armel.deb f074f46e9fb762c818ab6b37fd19955e30536dd51e431af3d2b148bf69334c1a 218784 libpq5_17.11-0+deb13u1_armel.deb b71a3278595b849d3ca0790b08444b3b87c9dae3b8c0fbd659e5ef85d5b5770e 18866696 postgresql-17-dbgsym_17.11-0+deb13u1_armel.deb 4c5845ad950d24dedb8c4959fb49b4a39195739ac33c2f2fe0d1c1fbf329e227 17441 postgresql-17_17.11-0+deb13u1_armel-buildd.buildinfo 358d024ce601c821c880795c1ad7c765ce54be359ebec46190f394df03c20bfb 15999772 postgresql-17_17.11-0+deb13u1_armel.deb 07975e6ab774a5dbf26c71f150f23ba9ef7bfa049d2c40df900f1949a1df8310 2826004 postgresql-client-17-dbgsym_17.11-0+deb13u1_armel.deb a8436035f634daa6b943ab0ce3992e172012e5dc7569e305430057dc37ff503e 1946844 postgresql-client-17_17.11-0+deb13u1_armel.deb ffbd91a3345907330bde60f10eb4f4ca8406eba206757163041fb7f63ec33256 197552 postgresql-plperl-17-dbgsym_17.11-0+deb13u1_armel.deb 1260db1ae862bca25436fd8c436fce189ffbdde5d51d6e16d8436a7bc90b19a1 89968 postgresql-plperl-17_17.11-0+deb13u1_armel.deb 99c6fc927ac0869b0913a7e194d809c54246cfdc49cde1a36345bfb8071c76da 198684 postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_armel.deb 7fbe82122e651df38c39e76a7174bc44dcf3597c9e98a2947de95fb1873b3e25 113764 postgresql-plpython3-17_17.11-0+deb13u1_armel.deb e5fe436ad078ce93c0a47ad67b7324dfb60c67e2824b59fac8c94e9d3999e409 82404 postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_armel.deb ac7d791ae7faf674440781df0b6475cb54df5a348ff2fddfae62136f58f5eec3 48016 postgresql-pltcl-17_17.11-0+deb13u1_armel.deb f2080e08549d84a93b541e3b81171fdd4a810fd762e085c48e4d637319a71335 55932 postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_armel.deb 871b6df4297af8c858c306255d3ab0f0b5b4d1a94abf40833f85b7f510960b81 1313028 postgresql-server-dev-17_17.11-0+deb13u1_armel.deb Files: 579145b500a0a337c1159c6450229617 16652 debug optional libecpg-compat3-dbgsym_17.11-0+deb13u1_armel.deb f20528e9829ec47e4b7512d6f397b8b8 23564 libs optional libecpg-compat3_17.11-0+deb13u1_armel.deb f1dcc6a464482b003b7192c4ddae0ee6 251252 debug optional libecpg-dev-dbgsym_17.11-0+deb13u1_armel.deb f9543b91ad07775de9c1920b5c980dd1 290408 libdevel optional libecpg-dev_17.11-0+deb13u1_armel.deb 3e9a5a295ef08e2cb98b3cd14d9cc85a 113140 debug optional libecpg6-dbgsym_17.11-0+deb13u1_armel.deb 237a195378e555c1e9f8b45d6b46ed2e 63708 libs optional libecpg6_17.11-0+deb13u1_armel.deb 915de7fe187201f4b267235ab5816594 90772 debug optional libpgtypes3-dbgsym_17.11-0+deb13u1_armel.deb c30ad487393f482ba698fd5d8bf5da3d 49780 libs optional libpgtypes3_17.11-0+deb13u1_armel.deb bee9d66a23206796a22018468f8408e2 147124 libdevel optional libpq-dev_17.11-0+deb13u1_armel.deb e338a26c162e7d7f75406c4ccef73136 293128 debug optional libpq5-dbgsym_17.11-0+deb13u1_armel.deb 16ea7770214616ab880751dabb861250 218784 libs optional libpq5_17.11-0+deb13u1_armel.deb cb19b09217e3046e9bff808f25d212ad 18866696 debug optional postgresql-17-dbgsym_17.11-0+deb13u1_armel.deb 2563d856d54fd598dfaa4a4b4ffe6979 17441 database optional postgresql-17_17.11-0+deb13u1_armel-buildd.buildinfo 15603564226893fa4c18505b1c0f5a84 15999772 database optional postgresql-17_17.11-0+deb13u1_armel.deb b53cbbe66ae115e2894ff55d56590cd5 2826004 debug optional postgresql-client-17-dbgsym_17.11-0+deb13u1_armel.deb ade28404deea6f83ea2aee09ca348960 1946844 database optional postgresql-client-17_17.11-0+deb13u1_armel.deb ab7d31028ace75f7534ef73a17edc10c 197552 debug optional postgresql-plperl-17-dbgsym_17.11-0+deb13u1_armel.deb 676f88a34bceddb092630a43f87733e9 89968 database optional postgresql-plperl-17_17.11-0+deb13u1_armel.deb af8725a1c8d34e2e66fbdd533ac3fdfc 198684 debug optional postgresql-plpython3-17-dbgsym_17.11-0+deb13u1_armel.deb 04efceb2514ad44d3d683636e1779369 113764 database optional postgresql-plpython3-17_17.11-0+deb13u1_armel.deb e173af2f233585929a0256432d4532b3 82404 debug optional postgresql-pltcl-17-dbgsym_17.11-0+deb13u1_armel.deb 7b35491382e495e9bd04909c61c92386 48016 database optional postgresql-pltcl-17_17.11-0+deb13u1_armel.deb 299c595e320a610d0b282f8e1356173b 55932 debug optional postgresql-server-dev-17-dbgsym_17.11-0+deb13u1_armel.deb 7f3f149fedeb09cc5dba7fe205b38ea1 1313028 libdevel optional postgresql-server-dev-17_17.11-0+deb13u1_armel.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE0Ha//LlsGOpbQ/H4xqCFmsOWgoYFAmp9kqQACgkQxqCFmsOW goZ8Rg//djDC8U8ULbkJnu1eO0BzFQyY2IH6YY3bnQc/ynXjLGbll2Ep85XzvIDX J0/gMuqKTH1ujoXq8Ch4VGEm454N87bYv0a0dTm2UBYQWU6ME4uNDHmYaPpVA7kB iDQi62zWG7h2BuuPcMI3kPYiNBd/Z4Y3N5Bpm4xlOWc+gmGZHDD+yrlRnCIgQrx3 TIVf4/LQjeCYm3AZHOvk0/MI7Kk7afzEyAVCG6+iGGaFgQZSXp2Z1aKOgPN3Mlp9 YwGh9ys0C4XtTeNJMROKGVkQlm01/Ot4ptnTUOt4UYOlsyLybO0ynK5e6nZaWzUU nGDn/Oeyj5/KJzc5uOW44ny4uwdfg0zVea9oJgWUadQXsohwD9Irgz2yARAwlk+r BnjZ4uAzrsB+JSAV32HyHtMeIjOUNFNKDgPjHXuVFpt38LK9xEtjhBI5WQUH6MhD 3VWqH3+88YeXkC9QJMbjID6XZyVG47vS+cfE+0EvCOtp11yDtHI21MmQeFUWtODl h1HR6m1nWtYdyopcCLG1h5jV6hwviA5YU5rik0G+i7cIgzADagEdCjPLixmrLaqL NzLL5Mw9nWuKAAm2uDh5PQBi2sKlJmQQEgD4jzYNwmjR5zb9E47stYVKlU6v5q6K zI+Pf5pT9bu+04dft/+r1qSl5bhZM1bB0GDj2Fs7tvM1UNixZR8= =6Xsh -----END PGP SIGNATURE-----