How to build openssl for Mac-Intel computers

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

How to build openssl for Mac-Intel computers

Jörg Eyring
Hi everybody,

we have a new platform - Macs with Intel processors.

Is there a chance to build a static library (i386 code) for linking in Xcode
2.2? A static library with ppc code has been done already. I'd like to end
up with a Universal Binary of my code.

Thanks a lot for any ideas!

-------------------------------------------------
TOPIX Informationssysteme AG, http://www.topix.de
Rudolf-Diesel-Strasse 14, D-85521 Ottobrunn
Tel: +49-89-608757-0, Fax: +49-89-608757-11
E-Mail: [hidden email]
-------------------------------------------------



______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: How to build openssl for Mac-Intel computers

wrowe
Jörg Eyring wrote:
> Hi everybody,
>
> we have a new platform - Macs with Intel processors.
>
> Is there a chance to build a static library (i386 code) for linking in Xcode
> 2.2? A static library with ppc code has been done already. I'd like to end
> up with a Universal Binary of my code.

For fun; doesn't configuring to build bsd x86 work for you?  Provided your
toolchain looks even remotely like a bsd box, where darwin is derived from,
the assembly code will be x86.



______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: How to build openssl for Mac-Intel computers

Jörg Eyring
Hi William,

thanks for your hint.

I'd give it a try, but I must admit that I'm neither a "Configure"- nor a
"Perl"-Guru :'(

A short description where to change the appropriate setting(s) would be
helpful.

Maybe someone has already done it?

Jörg

>> Hi everybody,
>>
>> we have a new platform - Macs with Intel processors.
>>
>> Is there a chance to build a static library (i386 code) for linking in Xcode
>> 2.2? A static library with ppc code has been done already. I'd like to end
>> up with a Universal Binary of my code.
>
> For fun; doesn't configuring to build bsd x86 work for you?  Provided your
> toolchain looks even remotely like a bsd box, where darwin is derived from,
> the assembly code will be x86.



______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

what exactly is the difference between ssl and ssh (secure shell)?

Chong Peng
In reply to this post by Jörg Eyring


if you google "ssl and ssh", you will find a few pages regarding this issue, such as:

http://www.snailbook.com/faq/ssl.auto.html
http://www.rpatrick.com/tech/ssh-ssl/

but all in all, what ssl accomplishes can be done by ssh and what ssh accomplishes can be done by ssl. it seems to me that this is just another example of complicities (confuses) created by human.

mybe a little bit off the topic. but any thoughts from this list?
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: what exactly is the difference between ssl and ssh (secure shell)?

Bernhard Fröhlich-2
Chong Peng wrote:

>if you google "ssl and ssh", you will find a few pages regarding this issue, such as:
>
>http://www.snailbook.com/faq/ssl.auto.html
>http://www.rpatrick.com/tech/ssh-ssl/
>
>but all in all, what ssl accomplishes can be done by ssh and what ssh accomplishes can be done by ssl. it seems to me that this is just another example of complicities (confuses) created by human.
>
>mybe a little bit off the topic. but any thoughts from this list?
>  
>
SSH is a specific protocol designed for remote login (though you can do
lots of other things with it). SSL a more generic protocol for secure
communications. You could write applications that do the same thing as
the ssh/sshd-applications using SSL as protocol. I have not seen
applications other than ssh/scp/sftp using the SSH protocol, though I
think they may be possible to realise.

IMHO the main difference if you want to develop new applications is the
existence of such a great and widely used API for SSL, for which I don't
know a counterpart for the SSH-protocol... ;)
If you want to go into details of security and usefulness, I guess it's
easy to start flame wars.

Hope it helps.
Ted
;)

--
PGP Public Key Information
Download complete Key from http://www.convey.de/ted/tedkey_convey.asc
Key fingerprint = 31B0 E029 BCF9 6605 DAC1  B2E1 0CC8 70F4 7AFB 8D26


smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: what exactly is the difference between ssl and ssh (secure shell)?

Richard Levitte - VMS Whacker
In reply to this post by Chong Peng
In message <[hidden email]> on Thu, 19 Jan 2006 11:03:09 -0800, "Chong Peng" <[hidden email]> said:

ChongPeng> if you google "ssl and ssh", you will find a few pages
ChongPeng> regarding this issue, such as:
ChongPeng>
ChongPeng> http://www.snailbook.com/faq/ssl.auto.html
ChongPeng> http://www.rpatrick.com/tech/ssh-ssl/
ChongPeng>
ChongPeng> but all in all, what ssl accomplishes can be done by ssh
ChongPeng> and what ssh accomplishes can be done by ssl. it seems to
ChongPeng> me that this is just another example of complicities
ChongPeng> (confuses) created by human.

There are quite a few perspectives from which to answer:

Trust: the trust model differs.  SSL uses the X.509 model, which is an
authority hierarchy (roughly, there's actually a lot more to say about
it).  SSH uses a much more personal style, where the individual user
is responsable for his keys and how they are to be used and
authenticated.

Cryptographic security: there's not really a lot of difference between
the two in this respect.  They use methods for key exchange and data
encryption that are fairly similar to each other.

Interface: SSH and SSL are widely different in this respect.  SSH
works as an application that you can call and tunnel whatever you wish
through, while SSL comes as a library of routines to use instead of
your usual network calls.  However, there are SSL applications that
provide the same kind of functionality as SSH; stunnel provides
tunneling, stelnet provides secure remote login.

There are probably other perspectives that I forget...

Cheers,
Richard

--
Richard Levitte                         [hidden email]
                                        http://richard.levitte.org/

"When I became a man I put away childish things, including
 the fear of childishness and the desire to be very grown up."
                                                -- C.S. Lewis
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: How to build openssl for Mac-Intel computers

Shriniwas-Kulkarni
In reply to this post by Jörg Eyring
Hi Jorg, you've mentioned in your message that 'A static library with ppc code has been done already.'

Could you pl. share here how you've done it ? I'm trying to do the same on my mac but can't even run the 'config' script that comes with the source.

Thanks a ton.

Reply | Threaded
Open this post in threaded view
|

Re: How to build openssl for Mac-Intel computers

Jörg Eyring
Hi,

> Hi Jorg, you've mentioned in your message that 'A static library with ppc code
> has been done already.'
>
>  Could you pl. share here how you've done it ? I'm trying to do the same on my
> mac but can't even run the 'config' script that comes with the source.
>
> Thanks a ton.

It should be quite easy. Have you read the "INSTALL" document?

Unzip the openssl.tar, read the "INSTALL" document, go into Terminal (you
should have Xcode installed), set the directory to the unzipped openssl dir,
type "./config", and then, when this has finished, type "make".

After that (it ran about 10 mins on my Mac) you'll find two ".a" libraries
in the openssl folder which can be used to link your program with.

Jörg



______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: How to build openssl for Mac-Intel computers

Shriniwas-Kulkarni
Hi Jorg, thanks a lot for your prompt reply!
My initial source was giving me problems, but when I picked the latest one, it compiled like magic!
Thanks once again!
Reply | Threaded
Open this post in threaded view
|

Re: How to build openssl for Mac-Intel computers

Shriniwas-Kulkarni
Hi Jorg, sorry to bother you again, but another quick question.
The libraries I built do not contain support for MD4 functions (e.g. MD4Init etc.) and hence I can't link these functions into my code.
Is there some build option that I need to specify to build them ? Thanks!
Reply | Threaded
Open this post in threaded view
|

Re: How to build openssl for Mac-Intel computers

Shriniwas-Kulkarni
In reply to this post by Shriniwas-Kulkarni
Oops! Those MD function names include an underscore inbetween and are like MD4_Init() instead of MD4Init().
My code is now building fine. Sorry to have bothered you! Thanks!