Hi Jakub,
I have my custom solution in place and it works well, but I'm always willing to
learn other ways to solve the problem.
I'll take a look this coming week. Thanks!
Sent from my mobile
> On Feb 20, 2015, at 3:34 PM, Jakub Zelenka wrote:
>
> Hi,
>
>> On Tue, Feb 10, 2015 at 3:31 PM, S
On Fri, Feb 20, 2015, Nathaniel McCallum wrote:
> I'd like to use ASN1_item_d2i_bio() (or something similar) to parse an
> incoming message. However, given that types like ASN1_OCTET_STRING
> have (essentially) unbounded length, how do I prevent an attacker from
> DOS'ing via OOM?
>
> Is there
Hi,
On Tue, Feb 10, 2015 at 3:31 PM, Sec_Aficionado
wrote:
> Matt,
>
> Thanks for keeping me honest! I see it now, but I totally missed it
> before. I must have just played with the cli and not read the full page.
>
> Can you please confirm that EVP is the way to go? I'll create my own
> little
Are the current iOS build instructions documented anywhere else? We
haven't built for iOS in several years, at which time xCode was still
using gcc. It appears xCode now uses clang and the signature embedding
no longer works. Looking at the following commit...
https://github.com/openssl/openssl
On 02/20/2015 10:52 AM, John Foley wrote:
> Appendix E.2 in the FIPS 2.0 users guide
> (https://www.openssl.org/docs/fips/UserGuide-2.0.pdf) contains blank
> pages on pages 134-136. Is this intentional? It appears the iOS build
> instructions starting on page 133 are incomplete.
John, I can tel
I'd like to use ASN1_item_d2i_bio() (or something similar) to parse an
incoming message. However, given that types like ASN1_OCTET_STRING
have (essentially) unbounded length, how do I prevent an attacker from
DOS'ing via OOM?
Is there some way to set a max packet size?
Nathaniel
__
Appendix E.2 in the FIPS 2.0 users guide
(https://www.openssl.org/docs/fips/UserGuide-2.0.pdf) contains blank
pages on pages 134-136. Is this intentional? It appears the iOS build
instructions starting on page 133 are incomplete.
___
openssl-users m
On Fri, Feb 20, 2015, jonetsu wrote:
> On Feb 19, 2015 10:50am Henrik Grindal Bakken wrote:
>
> > I'm not sure it will be called on every conceivable error in
> > the FIPS module, but what I do in similar situations is
> > something like this:
>
> > static int post_cb(int op, int id, int subid,
On Feb 19, 2015 10:50am Henrik Grindal Bakken wrote:
> I'm not sure it will be called on every conceivable error in
> the FIPS module, but what I do in similar situations is
> something like this:
> static int post_cb(int op, int id, int subid, void *ex)
> {
> if (op == FIPS_POST_FAIL)
>
On 02/20/2015 11:42 AM, Frans de Boer wrote:
Hi,
I have a server running 12.3 and want to install on a different
partition the newer 13.2 distribution. Alas, after installation I can't
boot 12.3 anymore because of wrong references. Every time I install a
fresh kernel I have to manually edit the
On 20/02/15 10:42, Frans de Boer wrote:
> Any suggestions?
Perhaps asking on an opensuse forum might get you a better response?
This is openssl!! :-)
Matt
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl
Hi,
I have a server running 12.3 and want to install on a different
partition the newer 13.2 distribution. Alas, after installation I can't
boot 12.3 anymore because of wrong references. Every time I install a
fresh kernel I have to manually edit the grub.cfg files to get 12.3
booted again.
12 matches
Mail list logo