- If you are getting BADSIG errors when updating your Backtrack install.. (Like below)
Reading package lists... Done W: GPG error: http://32.repository.backtrack-linux.org revolution Release: The following signatures were invalid: BADSIG AB6DA34B475A6B7F BackTrack Repository Admin <emgent@backtrack-linux.org> W: GPG error: http://all.repository.backtrack-linux.org revolution Release: The following signatures were invalid: BADSIG AB6DA34B475A6B7F BackTrack Repository Admin <emgent@backtrack-linux.org> W: GPG error: http://updates.repository.backtrack-linux.org revolution Release: The following signatures were invalid: BADSIG AB6DA34B475A6B7F BackTrack Repository Admin <emgent@backtrack-linux.org>
- You can run the following commands to clean things up and allow your updates to start working again. I found this on someone else’s website in regards to Ubuntu updates, so it doesn’t have anything directly to do with Backtrack as far as I can tell.
- I created a little script called fixsig.sh to resolve this issue as it seems to happen a lot to me. Probably because of something I’m doing causing the issue.
root@bt:~# cat fixsig.sh sudo apt-get clean cd /var/lib/apt sudo mv lists lists.old sudo mkdir -p lists/partial sudo apt-get clean sudo apt-get update root@bt:~#
Hope this helps someone!
It helped me!
Thanks!
Helped, thanks! For me I believe the problem stemmed from trying to use a weak wifi signal to apt-get update. It didn’t complete and left some junk behind.
Thanks, this worked for me was stuck from last couple of weeks.
Hey thanks! good idea, never thought of doing an automation script for it.
I am new to backtrack and seeing same error and I also dont know how to run this script , please little tutorial on how to run this script would be helpful
WOW THANKS DUDEEEE!!!!! it worked for me