On Thu, 6 Dec 2007, Darren J Moffat wrote:

> David Kleiner wrote:
>> On 8/16/07, *Valerie Bubb Fenwick* <Valerie.Fenwick at sun.com
>> <mailto:Valerie.Fenwick at sun.com>> wrote:
>>
>>     On Fri, 17 Aug 2007, Quaker Fang wrote:
>>
>>     > Hi,
>>     >
>>     > A community user (outside SWAN) need to download the snv_66 releated
>>     > SUNWcry package,
>>     > where could he download?
>>
>>     We don't have those up anywhere for download at this time... there
>>     is a project in the works (it's on my plate now) to make that package
>>     obsolete. I hope to make some progress on that soon, so community
>>     users won't need it.
>>
>>     Valerie
>>     --
>>
>>
>> Valerie,
>>
>> In the mean time, is it possible to use the released S8 SUNWcry(*) for
>> snv_*?   S10 happily accepted it, the last time I tried - it also
>> resolved patch signature verification problems.
>
> I don't know if this was answered or not but not only can you not use
> Solaris 8 packages on Nevada you MUST use the ones that *exactly* match
> the Nevada build you are running.  If you don't you are running a very
> high risk of getting crashes in at least applications using OpenSSL and
> possibly in some cases a kernel panic too.

Hi David  & Darren -

I'm not sure if this was ever responded to, I'm sorry about that.

You might be able to install S8 SUNWcry(*) packages on S10, but they
won't have the desired effect - they contain completely different
binaries than what shipped in the S10 SUNWcry* packages.

But, the best solution for you in the mean time is to get these binaries
from the SUNWcry & SUNWcryr packages in the on-closed-bins.*.tar files.
(which is a slight misnomer, because these are not actually closed
source files, but they are not normally included in the distribution)

Those are available here:
http://dlc.sun.com/osol/on/downloads/current/

Valerie
-- 
Valerie Fenwick, http://blogs.sun.com/bubbva
Solaris Security Technologies,  Developer, Sun Microsystems, Inc.
17 Network Circle, Menlo Park, CA, 94025. 650-786-0461

Reply via email to