The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Debian untrusted packages problem

    Discussion in 'Linux Compatibility and Software' started by wearetheborg, Sep 29, 2009.

  1. wearetheborg

    wearetheborg Notebook Virtuoso

    Reputations:
    1,282
    Messages:
    3,122
    Likes Received:
    0
    Trophy Points:
    105
    I tried to install cvs (a standard tool):
    It gave me the following warning:

    Code:
    Untrusted packages could compromise your system's security.
    You should only proceed with the installation if you are certain that
    this is what you want to do.
    
      cvs 
    
    Here is my sources.list file:
    Code:
    deb http://ftp.us.debian.org/debian/ lenny main contrib non-free
    deb-src http://ftp.us.debian.org/debian/ lenny main contrib non-free
    
    deb http://security.debian.org/ lenny/updates main
    deb-src http://security.debian.org/ lenny/updates main
    
    deb http://volatile.debian.org/debian-volatile lenny/volatile main
    deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
    
    deb http://www.debian-multimedia.org lenny main
    
    I have imported the debian-multimedia keyring, so everything should be authentic. Why am I getting this warning message ?
     
  2. timberwolf

    timberwolf Notebook Consultant

    Reputations:
    131
    Messages:
    288
    Likes Received:
    0
    Trophy Points:
    30
    I don't know what the problem is here, but I think it is worth clearing up a little misconception that you have.

    The debian-multimedia-keyring is only applicable to the third-party multimedia repository, the last one in your list. You should have other keyrings for the debian repositories - most likely debian-archive-keyring.

    Type the following to see the keyring packages that you have installed:

    dpkg -l '*keyring*' | grep ^i

    You can also look in /usr/share/keyrings to see what keyrings are in there.
     
  3. The Fire Snake

    The Fire Snake Notebook Virtuoso

    Reputations:
    426
    Messages:
    2,889
    Likes Received:
    0
    Trophy Points:
    55
    I am not a 100% sure, but it might be due to the volatile repos and it is trying to grab CVS from it. I have never used it myself. Why do you have it?
     
  4. timberwolf

    timberwolf Notebook Consultant

    Reputations:
    131
    Messages:
    288
    Likes Received:
    0
    Trophy Points:
    30
    I think it is unlikely that the cvs package would be coming from volatile but you can easily check which repository with:

    apt-cache policy cvs
     
  5. wearetheborg

    wearetheborg Notebook Virtuoso

    Reputations:
    1,282
    Messages:
    3,122
    Likes Received:
    0
    Trophy Points:
    105
    I have the following:
    Code:
    # apt-cache policy cvs
    cvs:
      Installed: 1:1.12.13-12
      Candidate: 1:1.12.13-12
      Version table:
     *** 1:1.12.13-12 0
            500 http://ftp.us.debian.org lenny/main Packages
            100 /var/lib/dpkg/status
    
    So its from main lenny :confused:

    My keyrings:
    Code:
    /usr/share/keyrings# ls
    debian-archive-keyring.gpg  debian-archive-removed-keys.gpg  debian-multimedia-keyring.gpg  debian-multimedia-removed-keys.gpg
    
     
  6. wearetheborg

    wearetheborg Notebook Virtuoso

    Reputations:
    1,282
    Messages:
    3,122
    Likes Received:
    0
    Trophy Points:
    105
    I'm not sure why I have the volatile repos ---- what does the volatile repo have ?
     
  7. timberwolf

    timberwolf Notebook Consultant

    Reputations:
    131
    Messages:
    288
    Likes Received:
    0
    Trophy Points:
    30
    Volatile contains packages such as virus scanners e.g. clamav.

    You could try commenting out volatile and then doing an update. There's a bug related to volatile and it's keyring not being in the Etch release and the maintainers repeated the mistake for the Lenny release. I don't see how it would apply as apt would have downloaded from the main repository.

    The other possibility is that your debian-archive-keyring has got corrupted?
     
  8. The Fire Snake

    The Fire Snake Notebook Virtuoso

    Reputations:
    426
    Messages:
    2,889
    Likes Received:
    0
    Trophy Points:
    55
    Comment it out and run an update. I have never used it. If I remember right it has very new versions of packages that haven't been tested very much. Debian prides itself by being a very stable distro, which it is. I have always used the main repos, security and multimedia and the only other repos I have used are from third party companies that keep their packages in their own server/area, like btnx or opera etc.

    Here is a little bit more info on it.
     
  9. wearetheborg

    wearetheborg Notebook Virtuoso

    Reputations:
    1,282
    Messages:
    3,122
    Likes Received:
    0
    Trophy Points:
    105
    The Fire Snake, thanks for the info :)

    Yeah I'm puzzled too. Apt did doanload from the main repo.
    How can I find out if the debian-archive-keyring has been corrupted ? How would I fix it ?
     
  10. timberwolf

    timberwolf Notebook Consultant

    Reputations:
    131
    Messages:
    288
    Likes Received:
    0
    Trophy Points:
    30
    I don't know the correct way (I thought of using debsums but the debian-archive-keyring doesn't have any file md5sum checksums and doh! I guess gpg keys are sort of checksums in themselves). Anyway, I had a little play around and the following command list 6 public keys for the debian archives. Both my Sidux and Etch system list Lenny and Lenny volatile. Playing with a hex editor on a copy of the file, I corrupted the last key and got an error when I reran the command.

    Alternatively, you could download the debian-archive-keyring .deb package and extract to a temporary directory and then md5sum checksum the temporary copy and then compare with md5sum of the installed files. I'm assuming based on listing the package contents (dpkg -L) that the files are simply copied rather than constructed?