gnupg_init

(PECL gnupg >= 0.4)

gnupg_init — Initialize a connection

说明

gnupg_init(?array $options = null): resource

参数

options

Must be an associative array. It is used to change the default configuration of the crypto engine.

**Configuration overrides**
key	type	description
file_name	string	It is the file name of the executable program implementing this protocol which is usually path of the `gpg` executable.
home_dir	string	It is the directory name of the configuration directory. It also overrides `GNUPGHOME` environment variable that is used for the same purpose.

返回值

A GnuPG resource connection used by other GnuPG functions.

更新日志

版本	说明
PECL gnupg 1.5.0	The `options` parameter was added.

示例

示例 #1 Procedural gnupg_init() example with default setting

<?php
$res = gnupg_init();
?>

示例 #2 Procedural gnupg_init() example with overriden file name and home dir

<?php
$res = gnupg_init(["file_name" => "/usr/bin/gpg2", "home_dir" => "/var/www/.gnupg"]);
?>

示例 #3 OO gnupg initializer example with default setting

<?php
$gpg = new gnupg();
?>

示例 #4 OO gnupg initializer example with overriden file name and home dir

<?php
$gpg = new gnupg(["file_name" => "/usr/bin/gpg2", "home_dir" => "/var/www/.gnupg"]);
?>

发现了问题？

了解如何改进此页面 • 提交拉取请求 • 报告一个错误

＋添加备注

用户贡献的备注 2 notes

down

der_axel at gmx dot de ¶

7 years ago

Set the correct GNUPG environment, before you call gnupg_init()!

The current FPM/FastCGI/Module User must have read - if you import write - permissions on that directory. You won't get an error message, if something is not correct.
Without a correct environment, all other gnupg functions will not work as you expected.

<?php
// Enter your .gnupg environment
putenv('GNUPGHOME=/var/www/vhosts/yourdomain/.gnupg');
error_reporting(E_ALL);
$res = gnupg_init();
gnupg_seterrormode($res,GNUPG_ERROR_WARNING);
$info = gnupg_keyinfo($res, 'your-key-id');
echo "Key - Info<pre>";
var_dump($info);
echo "</pre>";
?>

down

djmaze ¶

2 years ago

Make sure home_dir option is not too many characters or else private keys fail.

You will notice that functions take a long time (seconds).

Commandline test yield error:
> gpg: can't connect to the agent: IPC connect call failed

Executing `gpg-agent --daemon --homedir /very/long/path/to/.gnupg` gave the error.
> socket name for '/very/long/path/to/.gnupg/S.gpg-agent.extra' is too long

So you must check that home_dir + '/S.gpg-agent.extra' is:
* < 107 characters on Linux
* < 104 on BSD 4.4