Newsgroups: php.general,php.internals,php.qa Path: news.php.net Xref: news.php.net php.general:323452 php.internals:74907 php.qa:67347 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68642 invoked from network); 14 Jun 2014 15:45:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jun 2014 15:45:24 -0000 Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.17.20 mout.gmx.net Received: from [212.227.17.20] ([212.227.17.20:55989] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CB/61-59122-E0E6C935 for ; Sat, 14 Jun 2014 11:45:18 -0400 Received: from [192.168.0.100] ([91.67.244.80]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MEGIi-1Wy0wd0f2O-00FSJ7; Sat, 14 Jun 2014 17:45:15 +0200 Message-ID: <539C6E15.2030000@gmx.de> Date: Sat, 14 Jun 2014 17:45:25 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 Followup-To: php-general@lists.php.net, To: Tsvetan Nikolov , PHP QA , "php-general@lists.php.net" , PHP Internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:1/Rx7vdmnI7fS1Hh/5B5MzK0jWcM+bs8fPpLOZlHQIfMsWzlnvK /EUnN4wFutKvKlVayCh8Gqeu/M/OUYZoZbyJ5Vg0wS4KIShxzlZXL0ZvD3qpiwAvSVis30z roRxP/5Q8qMnFk1ZtaE8eosyUgda1szaOBz4ptKI1wXV7PLgnoaDHcUCxb1Ug560TSkHwTj KZn2oxo9VIsVEV81wJa0g== Subject: Re: gnupg_verify help needed From: cmbecker69@gmx.de (Christoph Becker) Tsvetan Nikolov wrote: > I've been fighting with gnupg_verify for days now and cannot understand how > it works. It returns an array in the form of: > > array ( 0 => array ( 'fingerprint' => 'BLABLABLA' 'validity' => 0 > 'timestamp' => 1402666925 'status' => 117440521 'summary' => 128 ) ) > > I don't understand which part of the array actually shows us that the > verification went well. Do I have to compare the fingerprint or the status > is enough. But then I get different statuses and don't know what they all > mean. Same with summary. On other occasions I get different unexplainable > results like status=>0 validity=>4. There is no documentation on what each > of these means. According to : | Verifies the given signed_text and returns information about the | signature. | ... | On success, this function returns information about the signature. On | failure, this function returns FALSE. So for basic verification it should suffice to check that the return value !== false. [xpost & fup2 php-general@lists.php.net] -- Christoph M. Becker