Mailing List Archive

Tru64 UNIX plans?
Is anyone currently working on adding support for Tru64 UNIX's enhanced
security to OpenSSH?
Re: Tru64 UNIX plans? [ In reply to ]
On Tue, Jan 18, 2000 at 11:01:29AM -0500, John P Speno wrote:
> Is anyone currently working on adding support for Tru64 UNIX's enhanced
> security to OpenSSH?

I got the time and did it myself with the help of the Tom Woodburn @
compaq (who wrote the enhanced security stuff originally in the other ssh).

Before I submit the patches, there's one issue that I'd like to get
feedback on.

Tru64 UNIX's libsecurity uses the log() function from libm and since
OpenSSH has its own log() routine, libsecurity cals that instead of the one
in libm and sshd will segfault.

I'd like to propose that the log() function be renamed.

Could that happen?

Take care.
Re: Tru64 UNIX plans? [ In reply to ]
On Fri, 7 Apr 2000, John P Speno wrote:

> I'd like to propose that the log() function be renamed.
>
> Could that happen?

Unlikely - I don't think that the OpenBSD folks would buy the change
and I won't make the change in my tree - it would make merging with
their sources a nightmare.

Can you work around it with linking order? Does Tru64 libc have _weak
symbols?

-d


--
| "Bombay is 250ms from New York in the new world order" - Alan Cox
| Damien Miller - http://www.mindrot.org/
| Email: djm@mindrot.org (home) -or- djm@ibs.com.au (work)
Re: Tru64 UNIX plans? [ In reply to ]
> > I'd like to propose that the log() function be renamed.
> >
> > Could that happen?
>
> Unlikely - I don't think that the OpenBSD folks would buy the change
> and I won't make the change in my tree - it would make merging with
> their sources a nightmare.

I kinda figured you said that. I could always try to convince them to
change it though. :-)

> Can you work around it with linking order? Does Tru64 libc have _weak
> symbols?

I'll look into this and other solutions. Thanks.