Re: How can I disable signature check for a Debian CD?
Kumar thank you for your help.
But Debian is identify their CDs in a different way. I don't know how to
doing this. The repository in the images are not signed. When I use CD
images after burn them to a blank CD, Debian successfully identify cdroms.
But when I try to use them as images after mount them to somewhere,
Debian doesn't identify local repository as trusted.
Maybe it is not possible at all. I want to do this because I have only
first DVD image of Debian. When I need another package which I dont have
one, I am adding a ftp url to my sources.list. When I do this Debian
is using only this url because my local repository is untrusted.
In the early times, I was manually sign my local Release. Maybe I should
continue to do this.
On Fri, Sep 10, 2010 at 08:49:32AM -0500, Kumar Appaiah wrote:
> On Fri, Sep 10, 2010 at 03:36:03PM +0300, Onur Aslan wrote:
> > On Fri, Sep 10, 2010 at 07:25:54AM -0500, Kumar Appaiah wrote:
> > > Please paste the error message here. It would contain the key ID.
> >
> > There is no error. Debian CD images doesn't have any signature or key.
>
> I see. I thought apt-get update would actually warn about the missing
> keys; maybe I was wrong.
>
> You could try looking for the Release.gpg file in your CD and trying
> out this:
>
> gpg --verify Release.gpg Release
>
> That would tell you the keys which were used to sign the files. For
> instance:
>
> gpg: Signature made Sat 04 Sep 2010 12:30:28 PM CDT using RSA key ID 55BE302B
> gpg: Can't check signature: public key not found
> gpg: Signature made Sat 04 Sep 2010 12:37:54 PM CDT using DSA key ID F42584E6
> gpg: Can't check signature: public key not found
>
> Please let me know if this helps.
>
> Kumar
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 20100910134932.GD27363@bowser.ece.utexas.edu">http://lists.debian.org/[🔎] 20100910134932.GD27363@bowser.ece.utexas.edu
>
Reply to: