Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) X-RT-Original-Encoding: iso-8859-1 Content-Length: 3905 From ESN@cotas.dk Thu Oct 4 10:44:02 2001 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.72.0.53]) by rt-11.mit.edu (8.9.3/8.9.3) with ESMTP id KAA08785 for ; Thu, 4 Oct 2001 10:44:02 -0400 (EDT) Received: from cotas2.cotas.vestas.dom (port54.vestas.dk [195.41.59.54]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id KAA01893 for ; Thu, 4 Oct 2001 10:44:01 -0400 (EDT) Received: by cotas2.cotas.vestas.dom with Internet Mail Service (5.5.2653.19) id ; Thu, 4 Oct 2001 16:42:57 +0200 Message-Id: <5016FCB2FD3A0940B420E2918F762F661869C0@cotas2.cotas.vestas.dom> Date: Thu, 4 Oct 2001 16:42:56 +0200 From: Esben Nielsen To: "'krb5-bugs@mit.edu'" Subject: vxWorks. >Number: 1002 >Category: pending >Synopsis: vxWorks. >Confidential: yes >Severity: serious >Priority: medium >Responsible: gnats-admin >State: closed >Class: sw-bug >Submitter-Id: unknown >Arrival-Date: Thu Oct 4 10:45:00 EDT 2001 >Last-Modified: Thu Oct 11 00:30:00 EDT 2001 >Originator: >Organization: >Release: >Environment: >Description: >How-To-Repeat: >Fix: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: mitchb State-Changed-When: Sun Oct 7 16:44:41 EDT 2001 State-Changed-Why: This isn't a bug report. The sender has been replied to with a suggestion to see our mailing list descriptions, send mail to krbdev@mit.edu, and possibly join kerberos@mit.edu and krbdev@mit.edu. From: Ken Raeburn To: Esben Nielsen Cc: krb5-bugs@MIT.EDU Subject: Re: pending/1002: vxWorks. Date: 11 Oct 2001 00:29:01 -0400 I'm not aware of any version of krb5 having been ported to vxWorks. Cygnus had a partial port of krb4, years ago, but never worked on porting krb5. I'd like to see some work done on Kerberos for embedded environments. My personal interest would be in PalmOS, which is much more drastically different from UNIX than vxWorks is. (Possibly enough so that starting with the current code base is questionable, but I certainly don't have enough time or energy to start on a new implementation right now.) Some of the requirements of many embedded systems, such as small memory footprints, may benefit us in the UNIX environment too. If you're taking the approach of supplying POSIX/BSD functions that vxWorks doesn't have, would an additional library to pre-load before loading Kerberos code, and maybe some extra header files to reference while compiling Kerberos, do the trick? That would probably be the least intrusive way as far as the Kerberos tree is concerned. The other approach you could take would be to modify some of the Kerberos code to use the appropriate vxWorks functions when compiling for vxWorks. Currently we have several instances of files with separate UNIX, Mac, and Windows implementations of certain functions, with conditional compilation. (Mostly in the lib/krb5/os directory, but in other places too I'm sure.) If we add more target operating systems, we should probably think about breaking the different versions out into different files. Have you any idea at this point how pervasive the changes are likely to be? Ken >Unformatted: I am right now trying to get Kerberos to run on vxWorks. I know this is probably not the right address to mail to, but this was the only one I could find in the documentation, but maybe you might tell me or lead me to a person who can help me. My questions are: - Has a recent version of Kerberos been ported to vxWorks already? - How should I handle the changes needed such that you can accept it into your development tree? I mostly need to add Posix and BSD functions which vxWorks does not provide. Esben Nielsen Cotas Computer Technology A/S Århus, Denmark