EXPKEYSIG error and fix

Forum Forums News Announcements EXPKEYSIG error and fix

This topic contains 13 replies, has 7 voices, and was last updated by rayburn Mar 23-10:59 am.

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #19367
    Forum Admin
    anticapitalista
    anticapitalista

    For those users getting the EXPKEYSIG error.

    Method 1:

    3 steps, in a terminal

    1. wget 'http://repo.antixlinux.com/antix-archive-keyring.asc'

    2. sudo apt-key add antix-archive-keyring.asc

    3. sudo apt-get update

    Method 2:

    1. Download antix-archive-keyring_20019.3.13_all.deb from here: http://repo.antixlinux.com

    In the directory where you downloaded the deb

    2. sudo dpkg -i antix-archive-keyring_20019.3.13_all.deb

    3. sudo apt-get update

    • This topic was modified 6 months, 1 week ago by anticapitalista.
    • This topic was modified 6 months, 1 week ago by anticapitalista.
    • This topic was modified 6 months, 1 week ago by anticapitalista.

    Philosophers have interpreted the world in many ways; the point is to change it.

    #19377
    Member
    caprea
    caprea

    Yes that fixes it.
    It happened on every installation here so far.

    #19380
    Forum Admin
    anticapitalista
    anticapitalista

    I was suspicious that the key would expire, but it was supposed to be valid until 2021

    Philosophers have interpreted the world in many ways; the point is to change it.

    #19392
    Member
    Avatar
    greyowl

    Method 1 worked for me.
    Thank you

    Dell Latitude D610 laptop (1.86 GHz, 2G RAM, 32 bit) - antiX 17

    #19395
    Member
    Avatar
    andfree

    Method 1 worked for me, too. After the 3rd step, I ran a “sudo apt-get dist-upgrade” and there was a package to be upgraded: antix-archive-keyring (20019.3.13 over 20017.3.14). So, shouldn’t we add it as “step 4”? Thanks.

    • This reply was modified 6 months, 1 week ago by andfree.
    #19411
    Member
    Avatar
    zeh

    I’ve tried the two methods with several repos but always got the 404 error

    axTest@axTest:~/Downloads
    $ wget 'http://repo.antixlinux.com/antix-archive-keyring.asc'
    --2019-03-14 16:56:02--  http://repo.antixlinux.com/antix-archive-keyring.asc
    Resolving repo.antixlinux.com (repo.antixlinux.com)... 72.143.17.194
    Connecting to repo.antixlinux.com (repo.antixlinux.com)|72.143.17.194|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 4053 (4.0K) [text/plain]
    Saving to: ‘antix-archive-keyring.asc’
    
    antix-archive-keyring.asc               100%[=============================================================================>]   3.96K  --.-KB/s    in 0.002s  
    
    2019-03-14 16:56:06 (2.52 MB/s) - ‘antix-archive-keyring.asc’ saved [4053/4053]
    
    axTest@axTest:~/Downloads
    $ sudo apt-key add antix-archive-keyring.asc
    OK
    axTest@axTest:~/Downloads
    $ sudo apt-get update
    Hit:1 http://security.debian.org testing/updates InRelease
    Hit:2 http://ftp.uk.debian.org/debian stretch-updates InRelease                                     
    Hit:3 http://ftp.gr.debian.org/debian testing InRelease                                             
    Ign:4 http://nl.mxrepo.com/antix testing InRelease                   
    Err:5 http://nl.mxrepo.com/antix testing Release
      404  Not Found [IP: 81.4.106.127 80]
    Reading package lists... Done
    E: The repository 'http://nl.mxrepo.com/antix testing Release' does not have a Release file.
    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.
    axTest@axTest:~/Downloads
    $ 
    
    axTest@axTest:~/Downloads
    $ sudo dpkg -i antix-archive-keyring_20019.3.13_all.deb
    (Reading database ... 156016 files and directories currently installed.)
    Preparing to unpack antix-archive-keyring_20019.3.13_all.deb ...
    Unpacking antix-archive-keyring (20019.3.13) over (20017.3.14) ...
    Setting up antix-archive-keyring (20019.3.13) ...
    
    Configuration file '/etc/apt/trusted.gpg.d/antix-archive-keyring.gpg'
     ==> Modified (by you or by a script) since installation.
     ==> Package distributor has shipped an updated version.
       What would you like to do about it ?  Your options are:
        Y or I  : install the package maintainer's version
        N or O  : keep your currently-installed version
          D     : show the differences between the versions
          Z     : start a shell to examine the situation
     The default action is to keep your current version.
    *** antix-archive-keyring.gpg (Y/I/N/O/D/Z) [default=N] ? y
    Installing new version of config file /etc/apt/trusted.gpg.d/antix-archive-keyring.gpg ...
    axTest@axTest:~/Downloads
    $ sudo apt-get update
    Hit:1 http://security.debian.org testing/updates InRelease
    Hit:2 http://ftp.uk.debian.org/debian stretch-updates InRelease                                                                        
    Hit:3 http://ftp.gr.debian.org/debian testing InRelease                                                                                
    Ign:4 http://nl.mxrepo.com/antix testing InRelease                   
    Err:5 http://nl.mxrepo.com/antix testing Release
      404  Not Found [IP: 81.4.106.127 80]
    Reading package lists... Done
    E: The repository 'http://nl.mxrepo.com/antix testing Release' does not have a Release file.
    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.
    axTest@axTest:~/Downloads
    $ 
    
    #19412
    Forum Admin
    anticapitalista
    anticapitalista

    Use repo-manager to change the antiX repo

    Philosophers have interpreted the world in many ways; the point is to change it.

    #19417
    Member
    Avatar
    zeh

    I’ve done that before (France, Netherlands, Greece, Portugal) and again now, to no avail

    Ign:4 https://mx-linux.ethz.ch/mx-packages/antix testing InRelease
    Err:5 https://mx-linux.ethz.ch/mx-packages/antix testing Release
      404  Not Found [IP: 129.132.53.171 443]
    Reading package lists... Done
    E: The repository 'https://mx-linux.ethz.ch/mx-packages/antix testing Release' does not have a Release file.
    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.
    update took 32.23 seconds
    Warning: The apt-get command failed
    Warning: There was a problem running apt-get update
    
    Checking source files ...
    It appears that at least one list file is missing
    Ign:4 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix testing InRelease   
    Err:5 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix testing Release
      404  Not Found [IP: 137.226.34.46 80]
    Reading package lists... Done
    E: The repository 'http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix testing Release' does not have a Release file.
    Ign:4 http://mirrors.rit.edu/mxlinux/mx-packages/antix testing InRelease
    Err:5 http://mirrors.rit.edu/mxlinux/mx-packages/antix testing Release
      404  Not Found [IP: 129.21.171.72 80]
    Reading package lists... Done
    E: The repository 'http://mirrors.rit.edu/mxlinux/mx-packages/antix testing Release' does not have a Release file.

    This information «N: See apt-secure(8) manpage for repository creation and user configuration details.» made me search and find
    https://manpages.debian.org/stretch/apt/apt-secure.8.en.html

    The last paragraph on Description reads:
    «A repository which previously was authenticated but would loose this state in an update operation raises an error in all APT clients irrespective of the option to allow or forbid usage of insecure repositories. The error can be overcome by additionally setting Acquire::AllowDowngradeToInsecureRepositories to true or for Individual repositories with the sources.list(5) option allow-downgrade-to-insecure=yes. Note: All APT-based package management front-ends like apt-get(8), aptitude(8) and synaptic(8) support this authentication feature, so this manpage uses APT to refer to them all for simplicity only.»

    I don’t have any idea though of whether this could be the solution.

    #19418
    Member
    caprea
    caprea

    Hi zeh,

    E: The repository ‘https://mx-linux.ethz.ch/mx-packages/antix testing Release’ does not have a Release file.

    In the above line is missing one time the word testing
    Should look

    https://mx-linux.ethz.ch/mx-packages/antix/testing testing
    not
    https://mx-linux.ethz.ch/mx-packages/antix testing

    In my opinion the repo-manager doesn’t handle testing-repos quite right

    Could you please edit your /etc/apt/sources.list.d/antix.list manually and add the missing testing

    #19424
    Member
    Avatar
    zeh

    Hi caprea,

    Could you please edit your /etc/apt/sources.list.d/antix.list manually and add the missing testing

    Yes, that was the problem and this was the solution.
    Thank you!

    #19520
    Member
    Avatar
    rej

    Hi-

    I was using the one-liner method for antiX and MX on all my devices, except one and used the 3 steps on that.

    It ended up putting a file called “antix-archive-keyring” in “Home”, right after the “Videos” folder (not “hidden”).

    Maybe I did it wrong?

    Can this be moved to somewhere else, hidden, or deleted?

    Thanks.

    #19521
    Forum Admin
    anticapitalista
    anticapitalista

    Delete it as it is no longer needed (assuming the 3 steps worked)

    Philosophers have interpreted the world in many ways; the point is to change it.

    #19522
    Member
    Avatar
    rej

    They worked – Thanks!

    #19667
    Member
    Avatar
    rayburn

    Thanks for the fix, method 1 worked for me on an infrequently used laptop.

    Nether of my two other machines suffered the problem, even though all are running 17.2 version.

Viewing 14 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic.