The problem initially reported was made worse by a couple of things. First,
Kris has not yet committed the changes to the openssh port so that it will issue
errors about the cryptography not being installed "correctly". This will not be
in all ports that use openssl when 4.0 is released. The ports which will not be
modified are the ones which are using configure to find openssl and have not had
build problems reported. (I have been looking at bento's error reports, but not
on the ports mailing list since I can't handle the additional e-mail volume.)
These include several ports which simply disable SSL when they do not link
correctly when they test for the existence of openssl (RSA symbols undefined).
(If you come across any ports like this, please let Kris and me know so we can
patch the port.) I also still have a couple ports in this class to be
completed. The ports Kris and I have fixed also will use the system version of
openssl over the port if it is installed. Unpatched ports may use either
version if the openssl port is installed.
Next, the error messages in ports/MK/bsd.ports.mk refer to a section of the
handbook which had not been committed when the release candidate was created
(and is still not on the web). We still need the packages (USA and
international) created to upgrade the cryptography to include RSA.
In conclussion, this will never be completed fixed (until all of the legal
issues disappear). People will need to manually install upgraded cryptography
as part of installing. The original complaint just points out that we are not
yet at the point where we want to be for the final release of 4.0, but that was
why 4.0RC was created.
Jim Bloom
[EMAIL PROTECTED]
Kris Kennaway wrote:
>
> On Sat, 12 Feb 2000, John Hay wrote:
>
> > and to me it looks like rsa.h is included:
> >
> > internat:/home/ftp/pub/FreeBSD/releases/i386/4.0-20000211-SNAP/des > cat des.?? |
>tar -tzvf - | grep rsa
> > -r--r--r-- root/wheel 12208 Feb 12 07:09 2000 usr/include/openssl/rsa.h
> >
> > Or is there something that I miss?
>
> That looks right. I think the original person was getting their crypto
> from the wrong place.
>
> Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
