openssl - Debian Package Tracker

general

source: openssl (main)
version: 3.5.4-1
maintainer: Debian OpenSSL Team (archive) (DMD)
uploaders: Christoph Martin [DMD] – Kurt Roeckx [DMD] – Sebastian Andrzej Siewior [DMD]
arch: all any
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1.1.1w-0+deb11u1
o-o-sec: 1.1.1w-0+deb11u3
oldstable: 3.0.17-1~deb12u2
old-sec: 3.0.14-1~deb12u2
old-upd: 3.0.17-1~deb12u2
stable: 3.5.1-1
testing: 3.5.3-1
unstable: 3.5.4-1
exp: 3.6.0~~beta1-1

versioned links

1.1.1w-0+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.1.1w-0+deb11u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.0.14-1~deb12u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.0.17-1~deb12u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.5.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.5.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.5.3-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.5.4-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.6.0~~beta1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libcrypto3-udeb
libssl-dev
libssl-doc (1 bugs: 0, 0, 1, 0)
libssl3-udeb
libssl3t64 (1 bugs: 0, 1, 0, 0)
openssl (50 bugs: 0, 28, 22, 0)
openssl-provider-fips (1 bugs: 0, 1, 0, 0)
openssl-provider-legacy

action needed

3 security issues in trixie high

There are 3 open security issues in trixie.

3 important issues:

CVE-2025-9230: Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
CVE-2025-9231: Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.
CVE-2025-9232: Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.

Created: 2025-09-30 Last update: 2025-10-01 07:31

3 security issues in forky high

There are 3 open security issues in forky.

3 important issues:

CVE-2025-9230: Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
CVE-2025-9231: Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.
CVE-2025-9232: Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.

Created: 2025-09-30 Last update: 2025-10-01 07:31

1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:

CVE-2025-9230: Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.

Created: 2025-09-30 Last update: 2025-10-01 07:31

2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:

CVE-2025-9230: Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code. Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
CVE-2025-9232: Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address. Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application. The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker. In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity. The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.

Created: 2025-09-30 Last update: 2025-10-01 07:31

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2025-09-06 Last update: 2025-09-30 23:03

5 security issues in buster high

There are 5 open security issues in buster.

1 important issue:

CVE-2024-5535: Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application. The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists). This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem. In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur. This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.

4 issues postponed or untriaged:

CVE-2023-5678: (postponed; to be fixed through a stable update) Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow. Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service. While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters. Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q. An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack. DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate(). Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application. The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
CVE-2024-0727: (postponed; to be fixed through a stable update) Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly. A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue. OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass(). We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.
CVE-2024-2511: (postponed; to be fixed through a stable update) Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
CVE-2024-4741: (postponed; to be fixed through a stable update)

Created: 2024-06-27 Last update: 2024-06-29 19:18

1 bug tagged patch in the BTS normal

The BTS contains patches fixing 1 bug, consider including or untagging them.

Created: 2025-01-06 Last update: 2025-10-01 08:31

RFH: The maintainer is looking for help with this package. normal

The current maintainer is looking for someone who can help with the maintenance of this package. If you are interested in this package, please consider helping out. One way you can help is offer to be a co-maintainer or triage bugs in the BTS. Please see bug number #332498 for more information.

Created: 2017-12-02 Last update: 2017-12-02 00:26

debian/patches: 5 patches to forward upstream low

Among the 5 debian patches available in version 3.5.4-1 of the package, we noticed the following issues:

5 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2025-10-01 06:03

testing migrations

excuses:
- Migration status for openssl (3.5.3-1 to 3.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ autopkgtest for borgbackup2/2.0.0b19-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Regression ♻ (reference ♻)
- ∙ ∙ autopkgtest for cyrus-imapd/3.12.1-2: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for debian-edu-config/2.12.904: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Ignored failure ♻ (reference ♻), ppc64el: Ignored failure ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
- ∙ ∙ autopkgtest for hippotat/1.2.2: amd64: Regression ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for httping/4.4.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for nodejs/20.19.4+dfsg-1: amd64: Regression ♻ (reference ♻), arm64: Pass, i386: Test triggered, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for nova/2:31.0.0-7: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for openssh/1:10.0p1-8: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for openssl/3.5.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ autopkgtest for pbbam/2.4.0+dfsg-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Reference test triggered, but real test failed already ♻, ppc64el: Reference test triggered, but real test failed already ♻
- ∙ ∙ autopkgtest for pdns/5.0.0-2: amd64: Pass, arm64: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for perl-openssl-defaults/7: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for petsc/3.22.5+dfsg1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pexpect/4.9-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pg-auto-failover/2.2-2: amd64: Pass, arm64: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pgagroal/1.6.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pgbackrest/2.56.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pgbouncer/1.24.1-1: amd64: Pass, arm64: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pgloader/3.6.10-4: amd64: Pass, arm64: Pass, ppc64el: Test triggered
- ∙ ∙ autopkgtest for pgpool2/4.6.3-2: amd64: Pass, arm64: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for php-net-ldap2/2.3.0-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for php8.4/8.4.11-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pipewire/1.4.8-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pistache/0.4.26+ds-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pmbootstrap/3.5.2-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for poedit/3.7-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pollen/4.21-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for postfix/3.10.4-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for postgresql-17/17.6-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for postgresql-18/18.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pound/4.17-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for privoxy/4.0.0-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for proftpd-dfsg/1.3.9~dfsg-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for proxytunnel/1.12.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pulseaudio/17.0+dfsg1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for puma/6.6.0-4: amd64: Pass, arm64: Ignored failure ♻, i386: Pass, ppc64el: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ autopkgtest for puppetlabs-http-client-clojure/2.1.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for pypy3/7.3.20+dfsg-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for python-a38/0.1.8-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for python-bitcoinlib/0.12.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for python-bonsai/1.5.3+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for python-cryptography/43.0.0-3: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Test triggered, s390x: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ autopkgtest for python-easywebdav/1.2.0-12: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for python-ecdsa/0.19.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for python-network/0.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for python-pygit2/1.18.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for python-signxml/4.2.0+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for python3.13/3.13.7-1: amd64: Pass, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ autopkgtest for python3.14/3.14.0~rc3-1: amd64: Pass, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, s390x: Test triggered
- ∙ ∙ autopkgtest for qca2/2.3.10-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for qcalcfilehash/1.1.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for qpid-proton/0.37.0-6: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for r-bioc-rtracklayer/1.66.0-3: amd64: Pass, arm64: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for r-cran-openssl/2.3.2+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for r-cran-pki/0.1-14-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for r-cran-s2/1.1.7-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rabbitmq-server/4.0.5-10: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for readpe/0.85.1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for redict/7.3.5+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for redis/5:8.0.2-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for resource-agents/1:4.16.0-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for roc-toolkit/0.4.0+dfsg-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for ros-ros-comm/1.17.4+ds-3: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rsync/3.4.1+ds1-5: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Test triggered, s390x: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ autopkgtest for rsyslog/8.2506.0-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rtpengine/12.5.1.46-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻ (reference ♻)
- ∙ ∙ autopkgtest for ruby-eventmachine/1.3~pre20220315-df4ab006-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for ruby3.3/3.3.8-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rust-cargo-c/0.10.11-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rust-condure/1.10.0-8: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for rust-debcargo/2.7.10-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rust-ognibuild/0.1.4-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rust-openssl-sys/0.9.109-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rust-parsec-tool/0.7.0-8: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rust-sequoia-git/0.4.0-4: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rust-sequoia-octopus-librnp/1.11.1-5: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for rustc/1.87.0+dfsg1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for rustup/1.27.1-4: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for s-nail/14.9.25-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for seqkit/2.9.0+ds-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for serf/1.3.10-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for silver-platter/0.5.44-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for sipcrack/0.2-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for skopeo/1.18.0+ds1-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for slic3r-prusa/2.9.3+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered
- ∙ ∙ autopkgtest for smartdns/46.1+dfsg-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for snac2/2.83-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for snid/0.4.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for snowdrop/0.02b-17: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ autopkgtest for soju/0.9.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for sp800-90b-entropy-assessment/1.1.8-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for spamassassin/4.0.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for spiped/1.6.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for sqlcipher/4.6.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for squid/7.1-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for srt/1.5.4-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for sscg/3.0.8-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for ssl-cert/1.1.3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for sslscan/2.1.5-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for sslsniff/0.8+git20111017-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for sssd/2.10.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for stenographer/1.0.1-7: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for streamlink/7.6.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for strongswan/6.0.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for stunnel4/3:5.74-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for sudo/1.9.17p2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for swi-prolog/9.2.9+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for swtpm/0.7.1-1.5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for swugenerator/0.5-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for syslog-ng/4.8.1-7: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for systemd/258-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for tcpdump/4.99.5-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for testssl.sh/3.2.1+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for tlswrapper/0~20250201-2: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for tor/0.4.8.16-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ autopkgtest for tpm-tools/1.3.9.2-0.2: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for tpm2-pkcs11/1.9.1-0.1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for tpm2-tools/5.7-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for trojan/1.16.0-1.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for u-config/0.33.3-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for uftp/4.10.2-1.1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for uget/2.2.3-2: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for unbound/1.24.0-2: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for unifrac-tools/1.4-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered
- ∙ ∙ autopkgtest for uwsgi/2.0.30-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for uwsgi-plugin-pypy/0.0.3: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for vagrant/2.3.7+git20230731.5fc64cde+dfsg-4: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for valkey/8.1.1+dfsg1-3: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for vlc-plugin-bittorrent/2.15-2: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for vsftpd/3.0.5-0.3: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for weborf/1.5-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for wesnoth-1.18/1:1.18.5-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for wireless-regdb/2025.07.10-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for workflow/0.11.11-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for wpa/2:2.10-24: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for x11vnc/0.9.17-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for xar/1.8.0.498-3: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for xml-security-c/3.0.0-2: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for xmltooling/3.3.0-3: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for yafc/1.3.7-5: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for yapet/2.6-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: Test triggered, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ autopkgtest for ylva/1.7-2: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ autopkgtest for zfs-linux/2.3.4-1: amd64: Pass, arm64: Pass, i386: Test triggered, ppc64el: Test triggered, s390x: Pass
- ∙ ∙ missing build on riscv64
- ∙ ∙ arch:riscv64 not built yet, autopkgtest delayed there
- ∙ ∙ Waiting for lintian test results (stalls migration) - info
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info:
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/o/openssl.html
- ∙ ∙ Reproducible on amd64 - info ♻
- ∙ ∙ Waiting for reproducibility test results on arm64 - info ♻
- Not considered

news

[rss feed]

[2025-09-30] Accepted openssl 3.5.4-1 (source) into unstable (Sebastian Andrzej Siewior)
[2025-09-21] openssl 3.5.3-1 MIGRATED to testing (Debian testing watch)
[2025-09-21] openssl 3.5.3-1 MIGRATED to testing (Debian testing watch)
[2025-09-18] Accepted openssl 3.6.0~~beta1-1 (source) into experimental (Sebastian Andrzej Siewior)
[2025-09-17] Accepted openssl 3.5.3-1 (source) into unstable (Sebastian Andrzej Siewior)
[2025-09-06] Accepted openssl 3.6.0~~alpha1-1 (source) into experimental (Sebastian Andrzej Siewior)
[2025-08-25] openssl 3.5.2-1 MIGRATED to testing (Debian testing watch)
[2025-08-10] Accepted openssl 3.5.2-1 (source) into unstable (Sebastian Andrzej Siewior)
[2025-08-07] Accepted openssl 3.0.17-1~deb12u2 (source) into proposed-updates (Debian FTP Masters) (signed by: Sebastian Andrzej Siewior)
[2025-07-28] Accepted openssl 3.0.17-1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Sebastian Andrzej Siewior)
[2025-07-20] openssl 3.5.1-1 MIGRATED to testing (Debian testing watch)
[2025-07-13] Accepted openssl 3.5.1-1 (source) into unstable (Sebastian Andrzej Siewior)
[2025-06-29] Accepted openssl 3.5.0-3 (source) into experimental (Sebastian Andrzej Siewior)
[2025-06-01] openssl 3.5.0-2 MIGRATED to testing (Debian testing watch)
[2025-05-28] Accepted openssl 3.5.0-2 (source) into unstable (Sebastian Andrzej Siewior)
[2025-05-24] Accepted openssl 1.1.1w-0+deb11u3 (source) into oldstable-security (Adrian Bunk)
[2025-04-26] Accepted openssl 3.0.16-1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Sebastian Andrzej Siewior)
[2025-04-11] openssl 3.5.0-1 MIGRATED to testing (Debian testing watch)
[2025-04-08] Accepted openssl 3.5.0-1 (source) into unstable (Sebastian Andrzej Siewior)
[2025-03-26] Accepted openssl 3.5.0~~beta1-1 (source) into experimental (Sebastian Andrzej Siewior)
[2025-03-12] Accepted openssl 3.5.0~~alpha1-1 (source) into experimental (Sebastian Andrzej Siewior)
[2025-02-21] openssl 3.4.1-1 MIGRATED to testing (Debian testing watch)
[2025-02-11] Accepted openssl 3.4.1-1 (source) into unstable (Sebastian Andrzej Siewior)
[2025-01-16] openssl 3.4.0-2 MIGRATED to testing (Debian testing watch)
[2025-01-06] Accepted openssl 3.4.0-2 (source) into unstable (Sebastian Andrzej Siewior)
[2024-11-03] Accepted openssl 1.1.1w-0+deb11u2 (source) into oldstable-security (Sean Whitton)
[2024-11-02] openssl 3.3.2-2 MIGRATED to testing (Debian testing watch)
[2024-10-31] Accepted openssl 3.0.15-1~deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Sebastian Andrzej Siewior)
[2024-10-31] Accepted openssl 1.1.1n-0+deb11u6 (source) into oldstable-security (Sean Whitton)
[2024-10-27] Accepted openssl 3.3.2-2 (source) into unstable (Sebastian Andrzej Siewior)

bugs [bug history graph]

all: 56
RC: 0
I&N: 32
M&W: 24
F&P: 0
patch: 1

links

homepage
buildd: logs, exp, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.5.2-1ubuntu1
28 bugs (2 patches)
patches for 3.5.2-1ubuntu1