Re: Introducing the RNP PHP bindings, the php-rnp library
| From: | Christoph M. Becker | Date: | Mon, 24 Oct 2022 12:02:50 +0000 |
| Subject: | Re: Introducing the RNP PHP bindings, the php-rnp library | ||
| References: | 1 2 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-17520@lists.php.net to get a copy of this message | ||
On 24.10.2022 at 04:41, Ronald Tse wrote:
> We have submitted a PECL account creation request since we haven’t heard back since we last
> posted.
>
> Would any moderator be able to help approve it so we can publish the extension? Thank you very
> much in advance!
I have approved the account request. From a quick look, php-rnp looks
good to be published on PECL. If you have any questions, feel free to ask..
Regards,
Christoph
> Kind regards,
> Ron
>
> _____________________________________
>
> Ronald Tse
> Ribose Inc.
>
> On Sep 5, 2022, at 10:25 AM, Ronald Tse
> <tse@ribose.com<mailto:tse@ribose.com>> wrote:
>
> Hello to everyone at PECL!
>
> I am Ronald Tse, writing on behalf of the RNP team. RNP is a high performance open-source
> OpenPGP library in C++, distributed with a BSD license. It is used by Mozilla Thunderbird for
> encrypted email handling across its 35+M user base.
>
> We have received requests from the PHP community to utilize RNP, and correspondingly we have
> created an official binding for PHP.
>
> The php-rnp library is still under development but is available at:
> https://github.com/rnpgp/php-rnp
>
> The php-rnp library is distributed under a BSD 3-clause license which is compatible with PECL.
>
> In order to distribute this library we would like to apply for a PECL account. Please feel free
> to let us know any questions in the meantime.
>
> We look forward supporting the PHP community in its encrypted email needs!
>
> Kind regards,
> Ron
>
> _____________________________________
>
> Ronald Tse
> Ribose Inc.
>
> +=========================================================+
> This message may contain confidential and/or privileged
> information. If you are not the addressee or authorized to
> receive this for the addressee, you must not use, copy,
> disclose or take any action based on this message or any
> information herein. If you have received this message in
> error, please advise the sender immediately by reply e-mail
> and delete this message. Thank you for your cooperation.
> +=========================================================+
>
>