All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
RE: Problem installing openssl-current
|
Logged in as: Guest |
Users viewing this topic: none |
|
Login  |
|
|
RE: Problem installing openssl-current - Aug. 4, '05, 12:01:00 PM
|
|
|
eperea
Posts: 71
Joined: Apr. 6, '05,
Status: online
|
Unsetting PKG_PATH did not change anything. /pkgs was where the packages downloaded from the ftp site were kept. (All of the files that pkg_add attempted to download were copied there.)
|
|
|
RE: Problem installing openssl-current - Aug. 4, '05, 1:31:24 PM
|
|
|
eperea
Posts: 71
Joined: Apr. 6, '05,
Status: online
|
Thanks for your help in tryin to track this down. I'll give it one more try this evening, but suspect I'll have to uninstall and reinstall SFU.
I thought of uninstalling pkg and installing the old version from the last Tools CD. (Or maybe the new CD will actually get here. :-)
|
|
|
RE: Problem installing openssl-current - Aug. 8, '05, 6:13:07 AM
|
|
|
philb
Posts: 1
Joined: Aug. 8, '05,
Status: offline
|
Hi all,
Just adding my voice to the clamour. I've had the same problem as eperea on Windows 2003 Server SP1.
This is based on a clean install of SFU (latest version of pkg, 2.4.3) so I doubt a resintall will help.
Regards,
-phil
|
|
|
RE: Problem installing openssl-current - Aug. 8, '05, 11:23:15 AM
|
|
|
Rodney
Posts: 3729
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Phil:
You need to provide some details of your system. The output from "uname -X" would be good.
Also have you installed other packages successfully?
In general, I'm leaning towards there being software from another source interfering.
We've run into AV, security and/or "rollback" software that can mess things up.
|
|
|
RE: Problem installing openssl-current - Aug. 10, '05, 6:46:54 AM
|
|
|
4players
Posts: 2
Joined: May 2, '05,
Status: offline
|
There are some double-entries in the +CONTENTS of openssl... remove the second entry for them (namely:
man/cat3/md5.3
man/cat3/mdc2.3
man/cat3/bn_print.3
man/cat3/hmac.3
man/cat3/rc4.3
man/cat3/ssl.3
man/cat3/pem.3
) and be happy, afterwards it installs here for good...
Ok... how do you do this? First of all you have to get the current package of openssl...
Then make a directory somewhere and change to this directory. "tar -xzpf /openssl-current-bin.tgz" (or wherever you stored the downloaded file) and do a "vi +CONTENTS" (or use your editor of choice, even WordPad does the work for you, but not notepad (newlines are not handled very well in notepad)). After you changed and saved the file you do a "tar -czpf /openssl-current-bin.tgz" to have a wonderful working openssl-binary-package which can be installed via "pkg_add -v /openssl-current-bin.tgz"...
|
|
|
RE: Problem installing openssl-current - Aug. 10, '05, 6:47:43 AM
|
|
|
4players
Posts: 2
Joined: May 2, '05,
Status: offline
|
Oops - forgot to say that the md5-sum of the entry should be deleted, too - the line after the match...
|
|
|
RE: Problem installing openssl-current - Aug. 10, '05, 9:36:06 AM
|
|
|
Rodney
Posts: 3729
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
I will say the "duplicate entry" thing is the first thing I looked for in my "source" files.
And there is only one entry per file in my source file.
I haven't changed the current version (honest) and the +CONTENTS also only has one entry.
I have found the real problem though. It is how you have installed SFU.
You did not choose to have case sensitivity with your install.
There are files in the package such as "BN_print.3" and "bn_print.3".
Without case sensitivity on the filesystem sees these as the same thing.
< Message edited by Rodney -- Aug. 10, '05, 10:37:37 AM >
|
|
|
RE: Problem installing openssl-current - Aug. 10, '05, 11:08:05 AM
|
|
|
Rodney
Posts: 3729
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Sorry, there is no entry in the FAQ about this (it hadn't reached a FAQ level until now).
So here's the info until the FAQ web page gets a new entry.
In the FAQ we recommend that you install with both Filesystem Case Sensitivity ON and Setuid ON.
The doom and gloom message at installation is mostly a message of Fear, Uncertainty and Doubt (FUD).
For best Unix behavior you need the functionality of both ON. Warning that Win32 is the only modern
system that may not cope well with case sensitivity in some instances is telling statement.
Anyway, to turn case sensitivity ON after installation edit the registry (run regedit.exe).
Go to the location HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel
and key "obcaseinsensitive" should get set to 0x0 to turn case sensitivity ON. Now Reboot.
-------------------------
A few points for future readers:
1) I'm going to add to the installer a check to warn people automatically about the case sensitivity if it's off.
This will make it easier for everyone.
2) Do turn ON both case sensitivity and setuid behaviors.
3) Avoid editing packages directly. The BN_print.3 and bn_print.3 are two completely different files and
they cover two completely different API's.
< Message edited by Rodney -- Aug. 10, '05, 11:38:25 AM >
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
|
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|