W: GPG error_Debian Etch, problems when updating

Hi people,
I hope someone can help me. I installed today debian unstable ( aka Etch ) on my laptop, and after istallation I run apt-get update to fetch latest packets from debian mirror. I got an error like this
Hit ftp://ftp.hr.debian.org testing/main Packages/DiffIndex
Hit ftp://ftp.hr.debian.org testing/contrib Packages/DiffIndex
Hit http://security.debian.org etch/updates/main Sources
Hit http://security.debian.org etch/updates/contrib Sources
Hit http://security.debian.org etch/updates/non-free Sources
Hit ftp://ftp.hr.debian.org testing/main Sources/DiffIndex
Hit ftp://ftp.hr.debian.org testing/contrib Sources/DiffIndex
Fetched 99.1kB in 6s (14.3kB/s)
Reading package lists... Done
W: GPG error: http://security.debian.org etch/updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A70DAF536070D3A1
W: GPG error: ftp://ftp.hr.debian.org testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A70DAF536070D3A1
W: You may want to run apt-get update to correct these problems

After that I rerun apt-get update as it suggessted me and got the same error. In /etc/apt/sources.list
I have
deb http://security.debian.org/ etch/updates main contrib non-free
deb-src http://security.debian.org/ etch/updates main contrib non-free

deb ftp://ftp.hr.debian.org/debian/ testing main contrib
deb-src ftp://ftp.hr.debian.org/debian/ testing main contrib

I have to mention that I have two more machines running Etch with same sources in sources.list but I do not have any problems with updating packages from that mirros. I am concerned about signatures mentioned in prevous error I got.
So if someone know how to solve this issue, and have a will to write it down will help me a lot.
I will use this chance to congragulation all debian people who contributed in developing debian Etch. Girls and guys you made fantastic work. I wish you the best

Sarajevo

See if the debian-archive-keyring package is installed that is where is the key is contained. Now it should be automatically put in the apt-key keyring once you install the package if not then as root.

gpg --keyring /usr/share/keyrings/debian-archive-keyring.gpg --armour --export 6070D3A1 | apt-key add -

This should put it into the apt-key keyring and get rid of the error.

Originally Posted by HappyTux See if the debian-archive-keyring package is installed that is where is the key is contained. Now it should be automatically put in the apt-key keyring once you install the package if not then as root. gpg --keyring /usr/share/keyrings/debian-archive-keyring.gpg --armour --export 6070D3A1 | apt-key add - This should put it into the apt-key keyring and get rid of the error.

Thank you very much HappyTux

Best wishes