Re: sysinstall and the status of des encryption?

[John Hay]

 
A quick question before I try to come up with a fix and
 patches for a problem that I believe to be a moving target.
 
I have run 'make release' to create 4.0-2306-SNAP with
 sources current as of 2am March 6th.  When running sysinstall
 and selecting ALL the encryption components, sysinstall
 fails trying to locate crypto/des.inf. When looking through
 /usr/src/release/Makefile, it doesn't appear that des.inf
 and des.?? are created anymore, but instead located in
 crypto.inf and crypto.??.
 
So, I believe sysinstall needs to be updated so des.??
 is not installed anymore.

H, so that is what it is. I also saw it break when I tried to
install a release with crypto stuff, but hadn't had a chance to
find out why it happened.

John
-- 
John Hay -- [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

sysinstall and the status of des encryption?

[John W. DeBoskey]

Hi,

   A quick question before I try to come up with a fix and
patches for a problem that I believe to be a moving target.

   I have run 'make release' to create 4.0-2306-SNAP with
sources current as of 2am March 6th.  When running sysinstall
and selecting ALL the encryption components, sysinstall
fails trying to locate crypto/des.inf. When looking through
/usr/src/release/Makefile, it doesn't appear that des.inf
and des.?? are created anymore, but instead located in
crypto.inf and crypto.??.

   So, I believe sysinstall needs to be updated so des.??
is not installed anymore.

   A 2nd question, do we need the concept of a default
crypto mechanism when installing ALL the encryption
components? Currently, it appears that 'last untarred'
wins for libcrypto.

   Comments Welcome!

Thanks,
John

-- 
John W. De Boskey
jwd@sasDOTcom

Gates' Law:   Every 18 months, the speed of software halves.
Gates' Corollary: Every 18 months, the size of software doubles.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message