RE: build openSSL for an embedded system without an OS

2009-02-18 Thread Guyotte, Greg
[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 'force brutish

Re: build openSSL for an embedded system without an OS

2009-02-18 Thread Ger Hobbelt
On Wed, Feb 18, 2009 at 4:24 PM, Guyotte, Greg gguyo...@ti.com 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

Re: build openSSL for an embedded system without an OS

2009-02-18 Thread Marek . Marcola
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 gguyo...@ti.com 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

build openSSL for an embedded system without an OS

2009-02-17 Thread Guyotte, Greg
Hi - I am wondering if it is possible to build openSSL (or actually a very small portion of it) for use in an embedded ROM on an ARM11-based system. For my purpose I only need to be able to perform RSA public key decryption within the ROM. Being a ROM, I have no OS support whatsoever. I

Re: build openSSL for an embedded system without an OS

2009-02-17 Thread Randy Turner
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

Re: build openSSL for an embedded system without an OS

2009-02-17 Thread Ger Hobbelt
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.