Hello,
owner-openssl-us...@openssl.org wrote on 02/18/2009 07:17:51 PM:
> On Wed, Feb 18, 2009 at 4:24 PM, Guyotte, Greg wrote:
> > Ger, thank you for this response. I really do just need the RSA
decryption bits, so I
> think that the approach you recommend is far too heavy-handed for me. I
On Wed, Feb 18, 2009 at 4:24 PM, Guyotte, Greg wrote:
> Ger, thank you for this response. I really do just need the RSA decryption
> bits, so I think that the approach you recommend is far too heavy-handed for
> me. I will check out the rsaref and cryptlib that you mentioned!
All right. Since
[mailto:owner-openssl-us...@openssl.org]
On Behalf Of Ger Hobbelt
Sent: Tuesday, February 17, 2009 8:40 PM
To: openssl-users@openssl.org
Subject: Re: build openSSL for an embedded system without an OS
I've done this sort of thing back before 2000. I'd label my approach
back then as 'fo
I've done this sort of thing back before 2000. I'd label my approach
back then as 'force brutish' as it was a mix of using the build system
and some code changes.
The trick is to search the configure system for a *hardware* (CPU!)
which is identical or at least very similar to your embedded one. D
Hi,
I think there is probably a *formal* way to do this within the
confines of the build system and design of OpenSSL, and there is
probably a brute-force way to do this.
I think just grabbing the crypto subtree and building a "make"
subsystem for this that makes no dependencies on platfo
