[From nobody Mon Jul  6 20:13:04 2026
Received: (at submit) by bugs.debian.org; 22 Jun 2026 17:16:41 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-118.6 required=4.0 tests=ALL_TRUSTED,BAYES_00,
 BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
 DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,SPF_HELO_NONE,
 SPF_PASS,USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 18; hammy, 150; neutral, 47; spammy,
 0. spammytokens:
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: <zeha@debian.org>
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:49676)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <zeha@debian.org>) id 1wbiGH-00FtOV-01
 for submit@bugs.debian.org; Mon, 22 Jun 2026 17:16:41 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Content-Type:MIME-Version:Message-ID:
 Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=iO165Eiur/rSIKYBcT9MTNtVxThsbiKYn1qdzUsxHF8=; b=QLKdV2EQJdakI2rJkVw70jLJU8
 R309JegRHk6iBekj0s5DfHMoBIcfCtR6cYkajpSY4Ys2L7YPbr7Aqkn23ptfOhxDEBP5gvG9cRyzX
 NKZDKrxfxFgc2NY43O1WxuIxSl7OL+Ph7ePPiCde80pZEOEyO9ppUZYiwNA8phTwf3llfEQB7SaHY
 yavibl/Amw4hK2PwkEMCwjwuYUhRx4PiXRBPhW/xS2Bycb0R/dmoiKa8xTrzknYwySB5R4ulXwaZ/
 tDpa41aiyqJxrZLXAyeKkFKScFVLipvyuhMDpanlGmK1ZU4ErhMuNrVprj5b8Kc3h/EHNhtaLBhiM
 60ITMUgg==;
Received: from authenticated-user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <zeha@debian.org>) id 1wbiGF-00125Y-0C
 for submit@bugs.debian.org; Mon, 22 Jun 2026 17:16:39 +0000
Date: Mon, 22 Jun 2026 19:16:36 +0200
From: Chris =?utf-8?Q?Hofst=C3=A4dtler?= <zeha@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Clarify openssl vs nettle usage in Debian
Message-ID: <ajlt9BzvN3tRponw@per.namespace.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
X-Reportbug-Version: 13.2.0
X-Debian-User: zeha
Delivered-To: submit@bugs.debian.org

Package: sq
Version: 1.3.1-10
Severity: important
X-Debbugs-Cc: holger@debian.org

Hi,

while researching sq on various operating systems, I've noticed that 
various other distros use the OpenSSL backend, while Debian's sq 
uses the nettle backend.

That seemed fine, however debcargo.toml also claims some openssl 
dependency:

https://sources.debian.org/src/rust-sequoia-sq/1.3.1-10/debian/debcargo.toml#L16

  [packages.bin]
  multi_arch = "foreign"
  depends = [ "openssl" ]

That left me wondering if Debian's sq was meant to use openssl 
instead of nettle.

Please clarify which backend was intended to be used.

Thanks,
Chris


PS: currently, ldd /usr/bin/sq shows:
	linux-vdso.so.1 (0x0000ffff9d7fb000)
	libsqlite3.so.0 => /usr/lib/aarch64-linux-gnu/libsqlite3.so.0 (0x0000ffff9c1a0000)
	libnettle.so.8 => /usr/lib/aarch64-linux-gnu/libnettle.so.8 (0x0000ffff9c130000)
	libhogweed.so.6 => /usr/lib/aarch64-linux-gnu/libhogweed.so.6 (0x0000ffff9c0c0000)
	libgmp.so.10 => /usr/lib/aarch64-linux-gnu/libgmp.so.10 (0x0000ffff9c010000)
	libgcc_s.so.1 => /usr/lib/aarch64-linux-gnu/libgcc_s.so.1 (0x0000ffff9bfd0000)
	libm.so.6 => /usr/lib/aarch64-linux-gnu/libm.so.6 (0x0000ffff9bf10000)
	libc.so.6 => /usr/lib/aarch64-linux-gnu/libc.so.6 (0x0000ffff9bd50000)
	/lib/ld-linux-aarch64.so.1 (0x0000ffff9d7b0000)
]