On Mon, Feb 2, 2015 at 3:58 AM, Leigh wrote:
> On 2 February 2015 at 10:57, Leigh wrote:
> > length (not sure how of
>
> Not sure how often tag lengths aside from 16 are used.
>
According to documentation provided about the OCB mode of AES it says the
following:
Section 3: The scheme
> The
On Sat, Jan 31, 2015 at 8:53 AM, Leigh wrote:
> Hi list,
>
> A couple of bug reports have highlighted the fact that our
> openssl_encrypt and openssl_decrupt functions have no way of getting
> or setting tags required for authenticated cipher modes (i.e. GCM,
> CCM, OCB (not sure if this is avail
HP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Jason Gerfen
http://www.github.com/jas-
<http://phpdhcpadmin.sourceforge.net>
pierrejoye
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Pierre Joye suggested that I request an account to help maintain the
OpenSSL extension as per our discussion on pull request #267.
--
Jas
Hello, I realize testing and bug fixes are taking place for the latest beta
release, so I apologize in advance if everyone is fairly busy.
I was just checking on the status of pull request #267 (
https://github.com/php/php-src/pull/267) addressing bug report #38917 (
https://bugs.php.net/bug.php?i
;
> thanks for the reminder.
>
> Am 13.02.2013 um 14:03 schrieb Jason Gerfen :
>
> > Is it considered spamming the list to check the status of a pull
> request? I
> > am going to ask any ways, hope it doesn't offend.
> >
> > The pull request addresses
Is it considered spamming the list to check the status of a pull request? I
am going to ask any ways, hope it doesn't offend.
The pull request addresses bug fix/feature request #38917 implementing
native signed public key & challenge support to the OpenSSL extension.
Details can be found @ https:/
Is there a procedure to take regarding removal of a push to the github repo
or do you simply close it. I would like to re-submit a push request against
the 5.5 branch while removing the old push request.
Also can I obtain some information on the current state of new function
extending regarding ac
Please bear with me as I am going to address a few things that (being new)
I seem to have over looked upon my initial pull request @
https://github.com/php/php-src/pull/21.
I have forked and submitted a push request to add native spkac
functionality per a feature request @ https://bugs.php.net/bug
On Tue, Jan 24, 2012 at 1:48 PM, Christopher Jones
wrote:
>
>
> On 01/24/2012 03:36 AM, Jason Gerfen wrote:
>>
>> I just have a general question regarding patch inclusions. When a
>> patch is submitted is there a formal review and testing of the patch
>> prior to
I just have a general question regarding patch inclusions. When a
patch is submitted is there a formal review and testing of the patch
prior to inclusion? From what I have been following from this list is
that the process is patches get applied to new/existing bug/feature
requests, bug fixes are pr
I posted this patch early last week to the list and did not see any
activity about it. According to the page (http://php.net/svn-php.php)
I should re-submit after a week just in case, so without further
adieu.
This is a simple implementation of four new functions to the OpenSSL
extensions to handl
Over the weekend I went ahead and created a patch to implement support
for SPKAC keys for the old/new KEYGEN element within the HTML5 spec.
According to feature requests at bugs.php.net I came accross this
existing request: https://bugs.php.net/bug.php?id=38917
I have filed a patch under this feat
14 matches
Mail list logo
