PGP signatures could not be verified

I'm still somewhat new on using makepkg. I previously customized the bind pkg for samba by copying the /var/abs/extra/bind directory into my /var/abs/local and adding a couple of build options. Worked like a charm and no issues.
Today bind 9.10.2 was released and I wanted to update my package but I get:
ERROR: One or more PGP signatures could not be verified! when updating using the latest abs bind package.
==> Making package: bind 9.10.2-1 (Wed Mar 4 16:47:20 PST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading bind-9.10.2.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 8282k 100 8282k 0 0 5669k 0 0:00:01 0:00:01 --:--:-- 5672k
-> Downloading bind-9.10.2.tar.gz.asc...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 490 100 490 0 0 6640 0 --:--:-- --:--:-- --:--:-- 6712
-> Found tmpfiles.conf
-> Found sysusers.conf
-> Found named.conf
-> Found named.service
-> Found localhost.zone
-> Found localhost.ip6.zone
-> Found 127.0.0.zone
-> Found empty.zone
==> Validating source files with sha1sums...
bind-9.10.2.tar.gz ... Passed
bind-9.10.2.tar.gz.asc ... Skipped
tmpfiles.conf ... Passed
sysusers.conf ... Passed
named.conf ... Passed
named.service ... Passed
localhost.zone ... Passed
localhost.ip6.zone ... Passed
127.0.0.zone ... Passed
empty.zone ... Passed
==> Verifying source file signatures with gpg...
bind-9.10.2.tar.gz ... FAILED
==> ERROR: One or more PGP signatures could not be verified!
this is the abs bind package....why is it failing?

Same error here.
==> Validando arquivos fonte com sha256sums...
firefox-36.0.1.source.tar.bz2 ... Passou
firefox-36.0.1.source.tar.bz2.asc ... Ignorada
mozconfig ... Passou
firefox.desktop ... Passou
firefox-install-dir.patch ... Passou
vendor.js ... Passou
rhbz-966424.patch ... Passou
firefox-fixed-loading-icon.png ... Passou
==> Verificando assinatura de arquivo fonte com gpg...
firefox-36.0.1.source.tar.bz2 ... FALHOU (chave pública desconhecida 057CC3EB15A0A4BC)
==> ERRO: Uma ou mais assinaturas PGP não puderam ser verificadas!
I have checked (http://allanmcrae.com/2015/01/two-pgp-k … rch-linux/) but to no avail.
I do not understand why complicate things when they are working perfectly how it worked before...

Similar Messages

One or more PGP signatures could not be verified!

Trying to install anything with pacaur or using makepkg gives out this error:
==> Making package: cower 12-2 (Wed Jan 7 07:11:25 WET 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading cower-12.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 22636 100 22636 0 0 60301 0 --:--:-- --:--:-- --:--:-- 60362
-> Downloading cower-12.tar.gz.sig...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 287 100 287 0 0 1136 0 --:--:-- --:--:-- --:--:-- 1134
==> Validating source files with md5sums...
cower-12.tar.gz ... Passed
cower-12.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
cower-12.tar.gz ... FAILED (unknown public key 1EB2638FF56C0C53)
==> ERROR: One or more PGP signatures could not be verified!
Can someone help?

clfarron4 wrote:
Potomac wrote:
jasonwryan wrote:Like everything else, this can be automated with a couple of lines in your ~/.gnupg/gpg.conf file, as described in the wiki.
I don't find this part in the wiki, can you tell me exactly where have you read this ?
https://wiki.archlinux.org/index.php/Gnupg
I saw automatic importing of missing keys in this BBS thread. Don't know if it is in the ArchWiki though.
Just found it here: https://wiki.archlinux.org/index.php/Ma … e_checking
It is a personal preference, I don't want to import Arch/AUR keys into my normal personal keyring - but reading the gpg (and makepkg) manpage it looks like if you set GNUPGHOME=/some/path first that should work to set a special keyring just for AUR and a custom config from the wiki.

[SOLVED] PGP signature could not be verified!

I am trying to install password safe from the AUR.
I have downloaded and un-tarred the tar.gz file but when I execute makepkg -s I get the following error:
$ makepkg -s
==> Making package: passwordsafe 0.94.1BETA-1 (Mon Dec 29 21:41:00 PST 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found pwsafe-0.94.1BETA-src.tgz
-> Found pwsafe-0.94.1BETA-src.tgz.sig
==> Validating source files with md5sums...
pwsafe-0.94.1BETA-src.tgz ... Passed
pwsafe-0.94.1BETA-src.tgz.sig ... Passed
==> Verifying source file signatures with gpg...
pwsafe-0.94.1BETA-src.tgz ... FAILED (unknown public key 919464515CCF8BB3)
Following the instructions on the "Package Signing" wiki, I:
$ sudo pacman -S haveged
$ sudo systemctl start haveged.service
$ sudo pacman-key --init
$ sudo pacman-key --populate archlinux
$ sudo pacman-key --add pwsafe-0.94.1BETA-src.tgz.sig
[sudo] password for xxxxx:
==> Updating trust database...
gpg: next trustdb check due at 2016-01-22
makepkg -s still fails at this point.
The next steps on the wiki call for:
1. verifying the fingerprint with: $ pacman-key -f keyid, and
2. locally signing the imported key with: # pacman-key --lsign-key keyid
How do I determine the "keyid"?
If I use the 'public key' returned in the error message above, I get:
$ pacman-key -f 919464515CCF8BB3
gpg: Note: trustdb not writable
gpg: error reading key: No public key
==> ERROR: The fingerprint of a specified key could not be determined.
And if I use the name of the file I downloaded with the tar, I get:
$ pacman-key -f pwsafe-0.94.1BETA-src.tgz.sig
gpg: Note: trustdb not writable
gpg: error reading key: No public key
==> ERROR: The fingerprint of a specified key could not be determined.
I even tried un-tarring the signature... but that didn't work either.
$ tar xzvf pwsafe-0.94.1BETA-src.tgz.sig
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
I also searched through pacman's keyring directly with:
$ gpg --homedir /etc/pacman.d/gnupg --list-keys
but I didn't see the packager's name or email address anywhere.
A nudge in the right direction would be greatly appreciated.
Cheers,
Last edited by sirdle (2014-12-31 01:05:32)

Thank you to everyone who replied!
It has taken me a while to read all the links and try to understand them.
My main problem was that I was mixing up package signing (via pacman) with package signing (via makepkg). The two are related, but separate: they both use gpg, they both use keys that can be downloaded from key servers, they both use keys that can be locally signed, they both use key-rings... but the key-rings they use are different, and process they use to install and validate those keys is also different. (Correct me if I'm wrong.)
From the Wiki
The signature checking implemented in makepkg does not use pacman's keyring.
In my case, I'm installing from the AUR. The error I received:
FAILED (unknown public key 919464515CCF8BB3)
was because makepkg could not find the supplied key in my personal key-ring.
All I needed to do was:
1. Download the key.
2. Add it to my personal key ring.
3. Trust it.
Alternatively, I could build the package by skipping the check.
Download the Key
1. Download from the MIT key server. Enter the keyid as a 16-digit hex number, e.g., 0x919464515ccf8bb3. Right-click on the result and save to the desktop [see Roken's post] above. Or,
2. Try the command line per jasonwryan's post above. (This number does not need to start with 0x.)
I tried both of these methods to verify that they work. They do.
Add the key to my personal keyring
With jasonwryan's method, the key is added as part of the command. With Roken's method an additional command is needed:
gpg --import /path/to/saved/keyfile
If I try makepkg -s at this point I still get an error... but the error is different. It is now:
FAILED (the public key A703C1328EABC7B201753BA3919464515CCF8BB3 is not trusted)
which brings us to the third step.
Trust It
$ gpg --list-keys # to get the correct keyid
$ gpg -edit-key keyid # from the previous command
gpg> trust
At this point, gpg asks the user how much he trusts this key. If you're like stevenhoneyman you might say, "Er... not very much" and opt for building without trust.
Or you can grant a lot of trust in order to create the package and then revoke the trust later (but I'm guessing this will cause problems when the package needs to be updated).
A level of 5 "Ultimate Trust" was required to build this package.
Thanks to everybody who helped me out with this. Definitely a learning experience!
Last edited by sirdle (2014-12-31 01:21:53)

Itunes update aborts - error "signature could not be verified"

I have attempted several times to download and install the latest iTunes update (11.2). The install keeps aborting with the error message "itunes signature could not be verified." I tried downloading only, and still get a similar error message. Please don't ask me for the error message number - I didn't record it.
I am running iTunes on Windows 8. I've been able to install previous updates since migrating to a Windows 8 machine. Is this a known issue? If so, how do I solve it?

I notice this has happened with previous versions of iTunes as well as previous versions of Windows. I don't see any posts as yet about 11.2. Am attempting to download via the Apple website as suggested in replies to previous instances of this error. I will let you all know the result. I'd really like to know WHY this happens! Is it related to iTunes or Windows? If someone could explain in reasonable layperson's terms, that would be helpful. This is obviously a known issue for quite some time (posts going back to 2010-2011); why hasn't it been addressed? We should be able to download iTunes updates from within iTunes!
Thanks!

VS 2013 Build tools installation fails with error "Signature or catalog could not be verified"

VS 2013 ultimate - Build tools installation fails with error "Signature or catalog could not be verified" for MSBuild assemblies. Any idea what could be the problem?
Thanks
NM

Hello,
Do you mean you are trying to use this tool:
https://www.microsoft.com/en-us/download/details.aspx?id=40760
Can you navigate to your %temp% folder and filter by date to see the log of the Build tool?
I want to know which assemblies failed to be verified.
By the way, since MSBuild is embed in Visual Studio why you want to install this again? Do you have any error about this Build Tool when you install Visual Studio 2013 Ultimate?
“Signature or catalog could not be verified” is always related to corrupt source
, please double check you have a healthy network and then try the web installer again.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Publisher could not be verified with new executable

We have a .exe file on our clients which is replaced yesterday with a new one. When a user on the client is starting the new executable then a message appears: publisher cannot be verified, do you no for sure to run this application?
The exe file is in the program files\subfolder\
The executable is starting with parameters: / servername.
It is the same executable as the one that was overwritten only a newer version so i do not understand why to give permission to start this exe.
I can choose in the message for execute but the next time it starts it must be done again. Because the users on the clients are not administrators they choose for execute in the message then they must give credentials. If in that screen the user chooses
for NO the program executes without credentials.
We do not want the question for publishing appearing, why is it suddenly appearing if it is the same name as the older one....
freddie

Hi,
This error happens so because the application chosen to run does not have a valid signature.
Would you please update the signature in your new version of exe file?
Please use following tool to verify the signature or sign your exe file:
Using SignTool to Verify a File Signature
http://msdn.microsoft.com/en-us/library/windows/desktop/aa388171(v=vs.85).aspx
If you know, what you open is always safe, we can try to disable this message:
Disable: The publisher could not be verified. Are you sure you want to run this software message
http://www.thewindowsclub.com/the-publisher-could-not-be-verified
Kate Li
TechNet Community Support

Publisher could not be verified message

I am very confused, I had itunes installe don my computer, and wante dto move it to an external hard drive I bought. I couldnt figure out how to move it so I uninstalled it and when I went to reinstall itunes on the external It now tells me the publisher could not be verified. I have tried to dump all temp files, and i have tried clicking run and save both. still nothing. Now we have three ipods that are worthless with out itunes....HELP!!!! please.....

okay. try downloading fresh definitions and running vigorous spyware and virus scans. if your security software providers offer them, try running "online" scans too. (they can sometimes pick up an infection even if the security software on the PC has been compromised.)
(checking on this because sometimes malware will disable Windows componentry relevant to the verification of digital signatures and publishers.)

HT5625 My daughter and I were both on same Apple ID. We are trying to change hers but when we do, it says her email is already associated with an Apple ID but when we try to get the password, it says that it could not be verified. How do we correct this?

My daughter and I were both on same Apple ID. We are trying to change hers but when we do, it says her email is already associated with an Apple ID but when we try to get the password, it says that it could not be verified. How do we correct this?

Not from your end. Click here and ask the iTunes Store staff for assistance.
(126716)

Problem with ID and download from app store:computer or device could not be verified

Hello.I have mac and i had one game from app store,but one day i couldnt open it,it ased me to ented my App ID and password,,,i did but it wrote to meYour device or computer could not be verified. Contact support for assistance. I allready chande my password and mad ned ID but nothing works.....the same problem.how can i download from app store again.thanks

Try a forum more suited:
https://discussions.apple.com/community/mac_app_store/using_mac_apple_store?view =discussions

I can't update IPhoto, it says "the product distribution file could not be verified it must be damaged or signed in" I bought it on iTunes and have 8,000 photos already. how can I update and correct this??

I can't update IPhoto, it says "the product distribution file could not be verified it must be damaged or signed in" I bought it on iTunes and have 8,000 photos already. how can I update and correct this??

You might try resetting the App Store application and clear the cookies via this menu:
as described in this website: Make use of the Mac App Store debug menu | MacFixIt - CNET Reviews
OT

SQL version could not be verified error while installing the SCOM 2012 R2 reporting component

I have the below SCOM server roles in my SCOM 2012 R2 set up
1) All servers with Windows Server 2008 R2 SP1, MS - SCOM1, DB & DW - DB1, Reporting Server - DB2
2) All the DB servers with SQL 2012 SP1
3) Windows firewall is turned off on all the servers.
4) Success fully installed all the components except SCOM reporting.
While installing the SCOM 2012 R2 reporting component on DB2 ( Iam running this set up on the server where I instllaed the SQL DB engine and reportin services in Native mode. Configured the SQL reporting database and reporting URLs successfully in SQL reporting
configuration manager) getting the below error in the Rporting server instance page. Kindly advise.
I ran mofcomp.exe and there is no firewall restrictions. My account also has DB owner & sysadmin permissions.
Also tried re installing the SQL on Reporting server.
"The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information".

Hi,
As far as I know, after installing SSRS, we don't need to configure the database and reporting URLs manully. When we install the reporting service for SCOM, it will configure those automatically.
If possible, you may re-install SSRS and then install SCOM reporting service.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely

After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely." What do I do now? This is an iMac and I'm running 10.6.8.

Clean Install of Snow Leopard
Be sure to make a backup first because the following procedure will erase
the drive and everything on it. See below for how to clone a drive.
     1. Boot the computer using the Snow Leopard Installer Disc or the Disc 1 that came
         with your computer. Insert the disc into the optical drive and restart the computer.
         After the chime press and hold down the "C" key. Release the key when you see
         a small spinning gear appear below the dark gray Apple logo.
     2. After the installer loads select your language and click on the Continue
         button. When the menu bar appears select Disk Utility from the Utilities menu.
         After DU loads select the hard drive entry from the left side list (mfgr.'s ID and drive
         size.) Click on the Partition tab in the DU main window. Set the number of
         partitions to one (1) from the Partitions drop down menu, click on Options button
         and select GUID, click on OK, then set the format type to MacOS Extended
         (Journaled, if supported), then click on the Apply button.
     3. When the formatting has completed quit DU and return to the installer. Proceed
         with the OS X installation and follow the directions included with the installer.
     4. When the installation has completed your computer will Restart into the Setup
         Assistant. Be sure you configure your initial admin account with the exact same
         username and password that you used on your old drive. After you finish Setup
         Assistant will complete the installation after which you will be running a fresh
         install of OS X. You can now begin the update process by opening Software
         Update and installing all recommended updates to bring your installation current.
Download and install Mac OS X 10.6.8 Update Combo v1.1.
You may be able to backup your data if you have an erased external drive you can use. Before you do the above but after you have opened Disk Utility you can try to clone your drive:
Clone using Restore Option of Disk Utility
1. Open Disk Utility.
2. Select the destination volume from the left side list.
3. Click on the Restore tab in the DU main window.
4. Select the destination volume from the left side list and drag
       it to the Destination entry field.
5. Select the source volume from the left side list and drag it to
      the Source entry field.
6. Double-check you got it right, then click on the Restore button.
Destination means the external backup drive. Source means the internal startup drive.
Now this will only work if the drive is accessible and can be cloned by Disk Utility. Otherwise, you would need to access your drive from another Mac that you can connect via Firewire - Target Disk Mode.

Your computer could not be verified Mac App Store and FaceTime

Hi All
I've been trying through several forums for a long time to find a solution for my problem before giving up, I'll go down to the point:
I have an iMac Intel 20" early 2008 (I can provide more detailed specs when required). I am using Mac OSX Lion installed from a usb and prior used Snow Leopard. They problem has been consistent thru all versions, same symptoms, same all.
1. Whenever I try to login to Mac App Store I get the famous: "your computer could not be verified, please contact support for assistance". FaceTime also does not login, promptying a "server error, try later".
2. Contacted support, and after 16 emails back and forth all I was told at the end was: "I am able to log in into your mac app store account from this side after resetting your account,is there anything I can do for you today".... (!!!!????)
3. There has been a problem parallel to that, and although I am not sure they are related anyhow I need to point it out. My ethernet port stopped working and there is no way to create any connection through it. I can still use wireless quite well (reason why I still keep my machine). After sending the machine to repairs, diagnose was that it could be a problem on the logic board and to fix it may require to replace LB entirely. So I decided not to go for it and keep the machine only with wireless connection.
So I have tried every single solution found (so far...) on google and forums to no avail: a) deleting .plist, b) resetting network configs and creating new locations, c) resetting PRAMs (not sure if it solve anything, but tried anyway) and others. The problem still persists with the same symptoms.
I can login into iTunes store and buy applications from computer, iPhone and iPad, which makes me think that my credentials are valid, alas, I logged into this forum using them.
I also tried creating a new account at App Store, when I request it through the Application, the "little fan that advises you to wait" appears, but suddenly dissapear with no warning or message at all (!!!!????). It is like you never requested anything in first place.
Obviously I can still use my machine for internet and stuff, but my ability to purchase/use any Apple software is seriously restricted. I cannot purchase any software anymore if AppStore is going to be the main way to acquire it (which I think it will).
So, my big questions are:
1) Is this hardware problem (ethernet, logic board, connection ports) remotely related to the machine authentication process when using MacApp Store and FaceTime through Apple?
2) Is there a way to fix this through software, before I consider replacing the machine? (Please take into account that I have already tried TS1811, deleting .plist files, resetting network, creating new locations from scratch... I basically searched thoroughly on google, forums and tips and tried all reasonable found recommendations before posting).
Thanks in advance.

Thanks Livia and Huevoos (eggs??) for your interest in this post.
In a nutshell, I haven't been able to solve this. I gave up on Apple support after they proved useless.
As Huevoos suggested, and I confirmed it time and again after browsing thru endless forums, it seems that the user validation routine for the Mac App Store is done by looking into your network settings, which in my case are either incomplete or erroneous due to the broken-down ethernet. (I am still waiting for somebody more experienced in this forum to contradict or explain this).
So, because I still have wireless connection, I can use my machine for day-to-day chores, have not been able to purchase anything up to this date in the Mac App Store though. I'm waiting for either a software update that could correct this (Mountain Lion??? there's no guarantee only hope) or the moment when my machine will need to be replaced by a new one with a functional ethernet.
I'm sorry I can't be of more help. But I'm pretty much in the same situation as you guys.
Live long and prosper.
Brt1618

Creation of this signature could not be completed.

I have been using Acrobat for quite some time now without issue. All of a sudden however I can't digitally sign my documents.
I receive the following error when I try to digitally sign:
"Creation of this signature could not be completed.
Platform Exception
The system cannot find the file specified.
Error Code: 2"
I have done some extensive searching and can't find a fix. I have deleted the following folder (as recommended in the forums), C:\Documents and Settings\[username]\Application Data\Microsoft\Crypto, but it doesn't help. The error continues to pop up.
I'm using Acrobat 7.1 on a PC w/Windows Media Center 2005, pentium 4, 2gb ram.

How do i extract the digital signature from the document signature field into a XML format?
Is there a way to create a XML signature and have a signature visible on the PDF form?
Thanks
Regards
Delvin

I am trying to buy Mountain Lion but I am getting this message: The product distribution file could not be verified. It may be damaged or was not signed.

I just tried to buy Mountain Lion but I am getting this message, yes, even after I reboot: The product distribution file could not be verified. It may be damaged or was not signed.
I don't understand what this means? Is my MacBookPro too old to work with Mountain Lion?

The Apple Support Communities are an international user to user technical support forum. As a man from Mexico my first language is Spanish. I do not speak English, however I do write in English with the aid of the Mac OS X spelling and grammar checks. I also live in a culture perhaps very very different from your own. When offering advice in the ASC, my comments are not meant to be anything more than helpful and certainly not to be taken as insults.
Always search the forum before posting. This is asked at least three times just below your post.
https://discussions.apple.com/thread/3604789?tstart=0
https://discussions.apple.com/thread/4153268?tstart=0

PGP signatures could not be verified

Similar Messages

Maybe you are looking for