[FC] bad fc.public.key on Trixie

6 views
Skip to first unread message

Felix Miata

unread,
Apr 14, 2025, 4:21:17 AMApr 14
to file-co...@googlegroups.com
This has been going on for a very long time, perhaps a year already. FC website
instructions for using fc.public.key do not work in Trixie, and fcl doesn't run
in Trixie.

# inxi -S
System:
Host: ara88 Kernel: 6.12.21-amd64 arch: x86_64 bits: 64
Desktop: TDE (Trinity) v: R14.1.4~[DEVELOPMENT] Distro: Debian GNU/Linux
trixie/sid
# apt-get update
Hit:1 http://ftp.debian.org/debian trixie InRelease
Hit:2 http://www.deb-multimedia.org trixie InRelease
Hit:3 http://silk.apana.org.au/debian buster InRelease
Err:3 http://silk.apana.org.au/debian buster InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 9AD8A8B17DF268DF78A1184CA82161048898875C is not bound: Policy rejected asymmetric algorithm because: DSA1024 is not considered secure since 2014-02-01T00:00:00Z
Reading package lists... Done
N: Ignoring file 'tde.lis' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://silk.apana.org.au/debian buster InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 9AD8A8B17DF268DF78A1184CA82161048898875C is not bound: Policy rejected asymmetric algorithm because: DSA1024 is not considered secure since 2014-02-01T00:00:00Z
W: Failed to fetch http://silk.apana.org.au/debian/dists/buster/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 9AD8A8B17DF268DF78A1184CA82161048898875C is not bound: Policy rejected asymmetric algorithm because: DSA1024 is not considered secure since 2014-02-01T00:00:00Z
W: Some index files failed to download. They have been ignored, or old ones used instead.
N: Some sources can be modernized. Run 'apt modernize-sources' to do so.
# fcl

(fcl:2008): Gtk-ERROR **: 04:15:51.249: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Trace/breakpoint trap
#
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Brian Havard

unread,
Apr 17, 2025, 3:41:34 AMApr 17
to file-co...@googlegroups.com
On 14/4/25 18:21, Felix Miata wrote:
> This has been going on for a very long time, perhaps a year already. FC website
> instructions for using fc.public.key do not work in Trixie, and fcl doesn't run
> in Trixie.

OK, I've now made a Trixie specific build with a new signing key and
added the details to the development page.

Felix Miata

unread,
Apr 18, 2025, 1:30:07 PMApr 18
to file-co...@googlegroups.com
Brian Havard composed on 2025-04-17 17:41 (UTC+1000):
From <https://silk.apana.org.au/fc2development.php>:
[quote]
Install the key file in /etc/apt/keyrings and filecommander-trixie.sources
in /etc/apt/sources.list.d/
[/quote]
Does "install" mean simply save your .key file to /etc/apt/keyrings/, or is
something more involved? I can't make it work:

# inxi -S
System:
Host: gb970 Kernel: 6.12.17-amd64 arch: x86_64 bits: 64
Console: pty pts/1 Distro: Debian GNU/Linux trixie/sid
# ls -gGh /etc/apt/keyrings/fc.public*
-rw-r--r-- 3 677 Apr 16 03:00 /etc/apt/keyrings/fc.public-2025.asc
-rw-r--r-- 3 677 Apr 16 03:00 /etc/apt/keyrings/fc.public-2025.gpg
-rw-r--r-- 3 677 Apr 16 03:00 /etc/apt/keyrings/fc.public-2025.key
# head -1 /etc/apt/keyrings/fc.public*
==> /etc/apt/keyrings/fc.public-2025.asc <==
-----BEGIN PGP PUBLIC KEY BLOCK-----

==> /etc/apt/keyrings/fc.public-2025.gpg <==
-----BEGIN PGP PUBLIC KEY BLOCK-----

==> /etc/apt/keyrings/fc.public-2025.key <==
-----BEGIN PGP PUBLIC KEY BLOCK-----
# apt-get update
Hit:1 http://ftp.debian.org/debian trixie InRelease
Hit:2 http://www.deb-multimedia.org trixie InRelease
Hit:3 http://archive.trinitydesktop.net/trinity/deb/trinity-sb trixie InRelease
Get:4 http://silk.apana.org.au/debian trixie InRelease [9,453 B]
Err:4 http://silk.apana.org.au/debian trixie InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key F1F26943B898146B2B67084587E7A67D10BB5BF8, which is needed to verify signature.
Reading package lists... Done
W: OpenPGP signature verification failed: http://silk.apana.org.au/debian trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key F1F26943B898146B2B67084587E7A67D10BB5BF8, which is needed to verify signature.
E: The repository 'http://silk.apana.org.au/debian trixie InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Some sources can be modernized. Run 'apt modernize-sources' to do so.
# time apt-get upgrade
...
Processing triggers for menu (2.1.51) ...

real 6m47.287s
user 1m11.023s
sys 0m23.146s
# dpkg-query -l filecommander
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-======================-============-=================================
ii filecommander 2.50.vgit-1851-buster1 amd64 File Commander/L
#

Could this failure have anything to do with this changelog report?:
[quote]
apt-listchanges: News
---------------------
debian-archive-keyring (2025.1) unstable; urgency=medium

Certificate (keyring) files in /usr/share/keyrings now have the
file extension .pgp, rather than .gpg. Compatibility links are
provided and will be removed in Debian 14 'forky'.
[/quote]

Felix Miata

unread,
Apr 20, 2025, 12:01:17 AMApr 20
to file-co...@googlegroups.com
I was trying to use the old sources format that doesn't point to the .key file. :p
Works fine following all instructions correctly. :)

Felix Miata composed on 2025-04-18 13:30 (UTC-0400):

> Brian Havard composed on 2025-04-17 17:41 (UTC+1000):
>
>> Felix Miata wrote:
>
>>> This has been going on for a very long time, perhaps a year already. FC website
>>> instructions for using fc.public.key do not work in Trixie, and fcl doesn't run
>>> in Trixie.
>
>> OK, I've now made a Trixie specific build with a new signing key and
>> added the details to the development page.
>
>>From <https://silk.apana.org.au/fc2development.php>:
> [quote]
> Install the key file in /etc/apt/keyrings and filecommander-trixie.sources
> in /etc/apt/sources.list.d/
> [/quote]
> Does "install" mean simply save your .key file to /etc/apt/keyrings/, or is
> something more involved? I can't make it work:
...
Reply all
Reply to author
Forward
0 new messages