openssh porting

[Moulding, Dan]

A couple of years ago, I ported OpenSSH to Nucleus. While Nucleus is not
exactly the same as vxWorks, the obstacles you'll need to overcome will
probably be very similar.

Mainly, you'll need a POSIX layer for vxWorks, which a few people have
already mentioned. Maybe someone has already done this for vxWorks. This
would be worth looking into. If not, you could port your own (from
OpenBSD for example), though I don't how easy this would be for vxWorks.
We did it for Nucleus, and it wasn't really all that bad.

I'd also recommend cutting out any OpenSSH functionality that you don't
absolutely need in your end product. This will reduce the amount of work
you'll need to do to port your own POSIX layer, if that's what you
decide to do. For example, if you don't need port forwarding, then
remove it. Same thing with PAM, Kerberos, etc. You can significanly
reduce the amount of work required if you carefully note your
requirements and then start removing modules that you know you won't
need.

-- Dan

-----Original Message-----
From: openssh-unix-dev-bounces+dmouldin=enterasys.com at mindrot.org
[mailto:openssh-unix-dev-bounces+dmouldin=enterasys.com at mindrot.org] On
Behalf Of mike zheng
Sent: Tuesday, November 16, 2004 5:28 PM
To: openssh-unix-dev at mindrot.org
Subject: openssh porting

Hi All,

I want port the openssh on an embedded system based on powerPC. Is there
any document that can guide me to start?

Thanks in advance,

Mike Zheng

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com 

_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev at mindrot.org
http://www.mindrot.org/mailman/listinfo/openssh-unix-dev