Makepkg signature verification

when I issue makepkg, I get the following output:
==> Making package: abs 2.4.4-2 (Wed Jan 21 05:31:23 UTC 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found abs-2.4.4.tar.gz
-> Found abs-2.4.4.tar.gz.sig
==> Validating source files with md5sums...
abs-2.4.4.tar.gz ... Passed
abs-2.4.4.tar.gz.sig ... Passed
==> Verifying source file signatures with gpg...
abs-2.4.4.tar.gz ... FAILED (the public key 487EACC08557AD082088DABA1EB2638FF56C0C53 is not trusted)
I have imported the key. I have signed the key. what is wrong?

gpg --recv-key 1EB2638FF56C0C53
fails to reach the server however using
sudo gpg --recv-key 1EB2638FF56C0C53] yields [gpg: key F56C0C53: "Dave Reisner <[email protected]>"
gpg: Total number processed: 1
gpg: unchanged: 1
however, this means the key is in root's keyring and I don't use makepkg as root. am I correct in this?
Last edited by shoelesshunter (2015-01-21 11:55:33)

Similar Messages

  • Signature verification changes in Adobe Reader 9

    [ I posted this message in the "Adobe Reader" forum, but I have realized that the post that I reference in my message belongs to this "Acrobat SDK" forum. So I've decided to send my post here, although this is not an Acrobat SDK question. Excuse me if you thing that my question should not be in this forum. ]
    Hi all,
    I have found this post in this forum talking about changes in Adobe Reader 9 related to signature verification:
        http://forums.adobe.com/message/2439480#2439480
    I have another scenario:
    A PDF with two signatures.
    After the first signature, a new page was added and then the PDF was signed again (using signature appearance).
    Using Adobe Reader 8.1.5, the result of signature verification is successful for both signatures.
    In fact, the byte range of the first signature is intact after adding the second signature.
    But if I open it with Adobe Reader 9.2.0, the verification result is invalid signature (for the first signature): the document has been modified and there is a new page.
    Since it seems that Adobe Reader 9 has added some new checks when verifying signatures, does anybody know (or know where can it be found) the list of new signature verification requirements of Adobe Reader 9 ?
    Or the list of changes allowed in Adobe Reader 9 that do not invalidate signatures ?
    Maybe a list similar to the changes allowed in the three types of certified signatures (TransformParams)?
    Thanks a lot in advance

    Thanks, lrosenth.
    The document I was searching for is in Adobe site and is called "Adobe Acrobat 9 Digital Signatures, Changes and Improvements".

  • Digital signature verification failed - Error RTCCTOOL

    Hi guys !!!
    I am running the report from the SDCCNN - RTCCTOOL, but I get the following error message:
    1. Digital signature verification failed
    Description -  The verification of the recommendation content using digital signatures has failed. Therefore recommendations were suppressed.
    Implementation -  Consult SAP note 69455 if there is a known issue with content verification. If you do not find a solution open a customer message on SV-SMG-SDD.
    When I Goto - Digital signatures Activate button digital content verification is disabled.
    Then go to the transaction on the client STRUST 000 and I found the certificate: SSF SAP AGS Online Content View The certificate shows:
    Owner: CN=SID SSF SAP AGS Online Content Verification, OU=I0020596183, OU=SAP Web AS, O=SAP Trust Community, C=DE
    Certificate List: CN=Online Recommendations, CN=OR-C, CN=V01M, OU=AGS, O=SAP AG, C=DE
                CN=Online Recommendations Upd, CN=OR-U, CN=V01M, OU=AGS, O=SAP AG, C=DE
    Both certificates will expire on 01.01.2038.
    According to the help and OSS note 69455 tell me again that I must create this certificate every year, but I see this current certificate, what is the error?
    What is the process because I'm not clear and can not find another OSS note or the SDN forum to tell me what is wrong is happening.
    Thanks guys for the help I can provide.
    Desiré

    Hi all.
    I have the same problem and explore all possible solutions found in this discussion and others without satisfactory result.
    Everything points that may be an inconsistency error external certificate which is in the DB. Anyone know how to fix this.
    Greetings.

  • Signature verification error

    I first used adobe signature, and then signed with other PDF reader, is a way to save incremental updates, but when use adobe to verification  the first signature, It said the file has been damaged.
    this test file url is : http://d.pcs.baidu.com/file/246895905e945c8048b2f29e8d3882ee?fid=3878797535-250528-8517461 08&time=1389174592&rt=pr&sign=FDTAER-DCb740ccc5511e5e8fedcff06b081203-vgmkM59aT5I%2FFrO%2B ilUvkqnjKCQ%3D&expires=8h&prisign=RK9dhfZlTqV5TuwkO5ihMQzlM241kT2YfffnCZFTaEMUMBfcIUvWxSGd xC0c48jqMKoU5v/JKZUmpAWJz7OVR968T9IbhxN0HyatJJyE/fx232pW9BdEEXBtrRUCrJk2HOV0gRi4YibEZeu5nB kjeT8NS0o+RrqZhZ3p7aL9Lpw=&r=471201396&cflg=65535%3A1
    Who can tell me the reason for the failure of the first signature verification , thank you.

    I am having the same issue. I turned off my add ons which it did go away but from what I was told it has something to deal with the ask toolbar or any toolbar associated with ask. Which I have no toolbar dealing with ask or even an ask toolbar.
    These are my addons:
    Adblock Plus-Added 2 weeks before issue, never had an issue with it before, use for to block ads that carry viruses, worms and trojans.
    G.a.i.arch toolbar -added recently after this re arose -This one is also a G.a.i.aonline bar-neither have search features so no ask dealing with them.
    Greasemonkey also added recently- blocks crap in signatures and autoplay on profiles on G.a.i.aonline(not the issue either)
    InboxDollars -three days on browser(this is my link to my inbox dollars account, where I can go to read my emails.
    Java Quick Starter - this was already disabled, have issue with the extra Javas.
    Microsoft .NET Framework Assistant- automatically part of the browser like Java Quick Starter
    Password Exporter-added to re add passwords.
    WorldTV Bar Community Toolbar-Added yesterday

  • Signature verification failed

    Hi all,
    I've been seeing a really weird problem with signing my HTML5 extension for Illustrator. I'm using the ZXPSignCmd tool to create a .zxp bundle and sign my extension from the command line. I'm able to install the extension using the Extension Manager, and I've also been able to distribute it to a private group through Adobe Exchange. It installs just fine, and runs great the first time, but after closing Illustrator and reopening it the extension often fails to load and just shows a blank window. I'm on a Mac, and looking at the log file here shows the following error when it happens:
    /Users/<<userName>>/Library/Logs/CSXS/csxs-ILST.log
    2014-12-17 10:18:02 : ERROR Signature verification failed for <<extensionID>>
    This is the only indication I have that it is a problem with the certificate. It seems really strange that it installs without errors and works once, but then fails when trying to load again. I was using a self-signed certificate, but I just bought a certificate from DigiCert to see if that would help, but I'm still having the same problem.
    This actually happens very rarely on my machine, but happens frequently to my other users. I assume this is somehow because I have been doing the development on this computer, so something is different about my extension environment.
    Has anyone else seen this issue at all? Does anyone have any tips that might help me to debug this? Other log files to look at, potential problems with the certificate or manifest file? I've tried about everything I could think of, so any help would be greatly appreciated!
    Thanks,
    James

    Nailed :-)
    For the folder you might save files into, there are few tokens in CEP:
    /* Identifies the path to user data.  */
    SystemPath.USER_DATA = "userData";
    /* Identifies the path to common files for Adobe applications.  */
    SystemPath.COMMON_FILES = "commonFiles";
    /* Identifies the path to the user's default document folder.  */
    SystemPath.MY_DOCUMENTS = "myDocuments";
    /* Identifies the path to current extension.  */
    /* DEPRECATED, PLEASE USE EXTENSION INSTEAD.  */
    SystemPath.APPLICATION = "application";
    /* Identifies the path to current extension.  */
    SystemPath.EXTENSION = "extension";
    /* Identifies the path to hosting application's executable.  */
    SystemPath.HOST_APPLICATION = "hostApplication";
    Otherwise you can rely on JSX folder tokens such as Folder.appData, Folder.userData etc (see a complete list on pages 56-57 of the JavaScript Tools Guide pdf) and create your extension's own folder.
    Mind you, CEP extensions should support both indexedDB and localStorage - one of them might fit your needs.
    Best
    Davide Barranca
    www.davidebarranca.com
    www.cs-extensions.com

  • Problems with signature verification in JDK1.5

    Hello to all!
    I have the a problem: I am trying to verify the signature with the following code:
        public static boolean verify(String data, String b64sign)
               boolean verified;
                BASE64Decoder dec = new BASE64Decoder();
                byte[] decoded = dec.decodeBuffer(b64sign);
                CertificateFactory factory = CertificateFactory.getInstance("X.509");
                FileInputStream fis = new FileInputStream("c:/cert/test-server.cert");
                X509Certificate cc = (X509Certificate) factory.generateCertificate(fis);
                System.out.println(cc);
                Signature signature = Signature.getInstance("SHA1withRSA");
                signature.initVerify(cc);
                signature.update(data.getBytes());
                verified = signature.verify(decoded);
                return verified;
        }and under jdk 1.5 the result is always FALSE. I've tried different providers, including "BC version 1.34", "SunJSSE version 1.5", "SunRsaSign version 1.5" but result is still the same.
    Curiously, that under jdk 1.4.2 all works fine, and signature verifies successfully. When running under jdk 1.4.2 provider used is: "SunJSSE version 1.42".
    What am I doing wrong?

    data.getBytes() isn't a reliable way of obtaining bytes from a String. Don't pass the data through a String, preserve it as bytes all the way through. Or use a fixed encoding when you do the translation, i.e. the same one that was used in JDK 1.4.2 whatever that was (by default). The default has changed between JDKs before now.

  • Cant update CF (Error occurred while installing the update:  Failed Signature verification)

    Hi I'm suffering with this issue Bug#3506758 - MySQL 5.6 Unable to Execute Queries
    and therefore am trying to update cf 10 to version 13 (current version is 8) however I get 'Error occurred while installing the update: Failed Signature verification'
    I'm running Mavericks on Mac.
    Can anyone point me to a step by step way to resovle this please (I'm new to Macs and am a cf coder but alas dont have any experience in server admin).
    Thanks very much indeed.
    Nick

    I was going to suggest that you needed to install the mandatory updater, but the Adobe help page for it says you shouldn't need to if you already have update 8 installed.  Might be worth verifying though.
    -Carl V.

  • Signature verification in Adobe Reader 10 takes a VERY long time...

    I work for a restaurant chain that uses PDFs for their new hire paperwork. We use a signature pad to sign the documents, and the documents have 51 signature boxes. Due to signature verification, it takes an absurdly long time to complete the paperwork (up to 60 minutes). Is there a way to disable the signature verification? It's incredibly frustrating to the management staff to have to sit in the office for an hour just to fill out a document that should only take about 15 minutes.

    I'm also experiencing the same issue where we go to open a document and it takes a long time to verify each of the signatures. Have you found a solution to this?

  • PPKLite Signature Verification Problem

    Hi all,
    I am a Windows developer, and I am using Microsoft CryptoAPI to develop a product that creates and verifies signatures in PDF documents.
    I am having trouble with PPKLite signature verification. Does this filter use some non-standard signature algorithm or procedure? Using CryptoAPI, I could not get a PPKLite signature to verify, although the format looks standard -- PKCS#7 and RSA/SHA algorithms.
    My code works just fine with the /Filter /VeriSign.PPKVS but not /Adobe.PPKLite. The CryptoAPI method succeeds on the former and reports an invalid signature on the latter. What's the difference between the two, cryptography-wise?
    Thanks very much in advance!!
    -- Peter

    lrosenth,
    Thanks for replying. Is there an email I use to send some files to you? They will be short: a simple PDF document signed by Acrobat Pro 7, the signer cert and the C++ code based on CryptoAPI that verifies the signature (and fails to do so.)
    Thanks again.
    -- Peter

  • SCUP publishing errors (signature verification fails)

    I have been unable to publish updates with full content in SCUP since getting it set up. Here is the environment:
    Config Manager 2012 R2 environment
    Installed SCUP on CAS (running Server 2008 R2)
    Configured SCUP to use proxy
    Here are the steps I followed to get it set up:
    Used IIS Manager to create a certificate request and got certificate from our vendor.
    Imported cert into local computer Personal certificate store.
    Following
    System Center Updates Publisher Signing Certificate Requirements & Step-by-Step Guide, exported .pfx with private keys for SCUP and exported .cer without keys into the Trusted Publishers and Trusted Root Certificate Authorities on the SCUP/CAS server.
    I also configured a GPO to deploy these to clients.
    Set up the Adobe catalogs, then tried to publish a reader update. Metadata updates work OK, but a full content publish generates errors.
    These are the germane errors I am getting (with server name changed to something generic):
    2015-01-07 20:16:04.100 UTC Error
    Scup2011.6 Publisher.PublishPackage
    PublishPackage(): Operation Failed with Error: Verification of file signature failed for file: \\ServerName\UpdateServicesPackages\9b8d0f21-d926-4a76-b64a-592b36247622\df7bfb6e-6c22-4bb7-9f15-b61ee3e09f96_1.cab
    1/1/1601 12:00:00 AM
    1997295659 (0x770C502B)
    PublishItem: InvalidException occurred during publishing: Verification of file signature failed for file: \\ServerName\UpdateServicesPackages\9b8d0f21-d926-4a76-b64a-592b36247622\df7bfb6e-6c22-4bb7-9f15-b61ee3e09f96_1.cab
    Updates Publisher 1/7/2015 3:16:04 PM
    6 (0x0006)
    Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured.
    Updates Publisher 1/7/2015 3:16:04 PM
    6 (0x0006)
    I have a followed or looked at a bunch of potential fixes but no dice. Any ideas?

    That might be the vendor of the cert but does not tell anything about the type of cert. It has to be a code signing one - otherwise it won't work.
    Torsten Meringer | http://www.mssccmfaq.de

  • Signature verification failed for PolicyAssignmentID

    I am in the process of setting up a new SCCM 2012 R2 server.  I have just begun to add some test boxes to the environment and every server thus far is registering in SCCM but is not pulling down its policies.  When doing a policy retrieval evaluation
    cycle the below is
    immediately spit out in the PolicyAgent.log file.  Any help would be
    appreciated!
    Signature verification failed for PolicyAssignmentID {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
    Raising event:
    instance of CCM_PolicyAgent_PolicyAuthorizationFailure
     ClientID = "GUID:F504615C-04F8-462D-B341-265C2FAEE7E7";
     DateTime = "20140708132926.819000+000";
     PolicyNamespace = "\\\\.\\ROOT\\ccm\\policy\\Machine\\RequestedConfig";
     PolicySource = "SMS:RET";
     ProcessID = 3532;
     ThreadID = 4320;

    It seems I have resolved my issue.  The cause was in the AD publishing.  I'm not sure if some parts were corrupt or simply missing but after removing the AD forest from 'Administration\Hierarchy Configuration\Active Directory Forests' in the
    SCCM admin console and re-adding it back SCCM was able to republish the needed info.  Then after a few minutes to allow for replication I was able to run a machine policy cycle which pulled all of my policies down!

  • Simple signature verification

    Hi everyone,
    I'm trying to get a simple working example of public key signature verification with openssl/java.security, but so far I haven't been able to get it to verify. Can someone please spot what I might of done wrong?
    openssl commands:
    openssl genrsa -out private_key.pem -3 768
    openssl rsa -in private_key.pem -pubout -out public_key.pem
    openssl dgst -md5 -sign private_key.pem -out sign.file test.file
    openssl dgst -md5 -verify public_key.pem  -signature sign.file test.file      // verifies OKThe file "test.file" only contains the text "message".
    So on to the java side of things. Since openssl encodes the publickey as base64, i used a small utility (http://www.fourmilab.ch/webtools/base64/) to decode it so i could read it in as a byte[]. It says that "-" is an invalid character so I removed the header (-----BEGIN PUBLIC KEY-----) and footer (-----END PUBLIC KEY-----) before i decoded it.
    the following is my code to try verify the public key/signature on the message.
         public static void main(String[] args)
              byte[] pkbytes = getFileBytes("/home/me/RSA/keys/pubkeybytes.pem"); // base64 decoded publickey
              System.out.println("pkbytes: " + new String(pkbytes));
              byte[] sigbytes = getFileBytes("/home/me/RSA/keys/sign.file");
              System.out.println("sigbytes: " + new String(sigbytes));     
              try
                   KeyFactory keyFactory = KeyFactory.getInstance("RSA");
                 EncodedKeySpec publicKeySpec = new X509EncodedKeySpec(pkbytes);
                 PublicKey publicKey = keyFactory.generatePublic(publicKeySpec);
                 //sign
                 Signature sig = Signature.getInstance("MD5withRSA");
                 sig.initVerify(publicKey);
                 // read in message
                  FileInputStream fis = new FileInputStream("/home/me/RSA/keys/test.file");  // just contains "message"
                  byte[] dataBytes = new byte[8192];
                  int nread = fis.read(dataBytes);
                  while (nread > 0)
                       sig.update(dataBytes, 0, nread);
                       nread = fis.read(dataBytes);
                  // verify
                  System.out.println ("Verification: " + sig.verify(sigbytes));
              catch (Exception e)
                   System.out.println(e.toString());
                   e.printStackTrace();
         public static byte[] getFileBytes(String filename)
              byte[] sigBytes = null;
              try
                   FileInputStream in = new FileInputStream(filename);
                   sigBytes = new byte[8192];
                   int count = in.read(sigBytes);
                   in.close();
              catch (Exception e)
                   System.out.println(e.toString());
                   e.printStackTrace();
              return sigBytes;
         }I'm really not sure what is wrong, but it is probably something obvious since I'm fairly new at this.
    Any help is really appreciated,
    Thanks.

    You didn't mention what the output was; did it throw exceptions? Instead of using some ad-hoc base64 decoder, just output the public key in the correct form directly from openssl, like the following:
    openssl rsa -in private_key.pem -pubout -out public_key.der -outform DER.
    NOTE: If you are not going to do something useful with an exception, then DO NOT catch it.

  • %IPS-3-Invalid__digital_signature (signature verification fauilure)

    hi,
    i try to load the IOS-S416-CLI.pkg into my C1841 ISR, using CLI
    problem is signature cannot extract and show me this error message %IPS-3-Invalid__digital_signature (signature verification fauilure)
    while i am using version 5 realm-cisco.pub signature, download from cisco tools
    anyone any idea for this?

    Hello,
    This error message literally means that the crypto signature on your router and the crypto signature in the IPS signature update do not match. This can be the result of an incorrect pubkey in your router configuration or a corrupt signature package. If you transfer the signature update from one computer to another after downloading it from Cisco.com, be sure to do the transfer in binary mode. Transferring the file in ASCII mode will remove various characters from the binary file and make the file unusable. If you have not transferred the file after downloading it from Cisco.com, or you are certain that you have not used ASCII mode to transfer the file, try downloading the file again from Cisco.com. The original download may have been corrupt.
    Below is the pubkey to compare with your router configuration:
    crypto key pubkey-chain rsa
    named-key realm-cisco.pub signature
    key-string
    30820122 300D0609 2A864886 F70D0101 01050003 82010F00 3082010A 02820101
    00C19E93 A8AF124A D6CC7A24 5097A975 206BE3A2 06FBA13F 6F12CB5B 4E441F16
    17E630D5 C02AC252 912BE27F 37FDD9C8 11FC7AF7 DCDD81D9 43CDABC3 6007D128
    B199ABCB D34ED0F9 085FADC1 359C189E F30AF10A C0EFB624 7E0764BF 3E53053E
    5B2146A9 D7A5EDE3 0298AF03 DED7A5B8 9479039D 20F30663 9AC64B93 C0112A35
    FE3F0C87 89BCB7BB 994AE74C FA9E481D F65875D6 85EAF974 6D9CC8E3 F0B08B85
    50437722 FFBE85B9 5E4189FF CC189CB9 69C46F9C A84DFBA5 7A0AF99E AD768C36
    006CF498 079F88F8 A3B3FB1F 9FB7B3CB 5539E1D1 9693CCBB 551F78D2 892356AE
    2F56D826 8918EF3C 80CA4F4D 87BFCA3B BFF668E9 689782A5 CF31CB6E B4B094D3
    F3020301 0001
    Quit
    Thank you,
    Blayne Dreier
    Cisco TAC IDS Team
    **Please check out our Podcast**
    TAC Security Show: http://www.cisco.com/go/tacsecuritypodcast

  • Adobe Acrobat X Pro: signature verification failing on 64bit Windows 7

    Hi,
    I have developed a plug-in for digital signing, creating standard PKCS#7. For verification, using default "Adobe Default Security" plug-in.
    "Adobe Default Security" verifying my created signatures successfully on Windows 7 32bit machine but failing to verify signature created on Windows 7 64bit machine.
    Message shown on 64bit machine is below:
    Why only on 64bit machine document tampering check failing but the procedure of creating PKCS#7 is same?
    So kindly do help me in this regard ASAP. What could be the reason there?
    Regards,
    Jhan Zaib

    Is a hardware token involved at all?  Do you not have a 64bit driver for it?

  • Signature verification registry key

    Hello All,
         I  have been trying to find the registry key that handles the "default  method for verifiying signatures". We are trying to apply this user  specific key to the local machine; so when any of the users log in, they  will not have to navigate to perferences - security - advanced  perferences - always use the default method (and manually select the  Topaz signature pad) for verification. Any leads would be appreciated.

    Use:
    -Dweblogic.security.SSL.allowSmallRSAExponent=true

Maybe you are looking for