On Sun, May 08, 2011, The Doctor wrote:
> On Sun, May 08, 2011 at 02:02:59PM -0600, The Doctor wrote:
> > Finally got fips to work, however
> >
> > 1) In either README or READ.FIPS, please state to compile FIPS, please use
> > GNU make. BSD make was choking
> >
> > 2) openssl version -a y
On Sun, May 08, 2011 at 02:02:59PM -0600, The Doctor wrote:
> Finally got fips to work, however
>
> 1) In either README or READ.FIPS, please state to compile FIPS, please use
> GNU make. BSD make was choking
>
> 2) openssl version -a yields
>
> OpenSSL 1.1.0-fips-dev xx XXX
> built
Finally got fips to work, however
1) In either README or READ.FIPS, please state to compile FIPS, please use
GNU make. BSD make was choking
2) openssl version -a yields
OpenSSL 1.1.0-fips-dev xx XXX
built on: Sun May 8 10:06:19 MDT 2011
platform: debug-bsdi-x86-elf
options: bn(64
Sorry, I posted it to the wrong list by mistate.
08.05.2011, 02:30, "Anton Vodonosov" :
> Hello.
>
> Is it safe to retrieve a socket handle like this:
>
> (ccl::ioblock-device (ccl::stream-ioblock socket t))
>
> and then perform some IO on it directly (in foreign code).
>
> Can this lead to a
Hello. Is it safe to retrieve a socket handle like this: (ccl::ioblock-device (ccl::stream-ioblock socket t)) and then perform some IO on it directly (in foreign code). Can this lead to any problems (like the Windows crush we are discussing in the ccl-devel)? Best regards,- Anton
_
On May 7, 2011, at 11:14 PM, Justin Schoeman wrote:
> Michael Tüxen wrote:
>> On May 7, 2011, at 10:40 PM, Justin Schoeman wrote:
>>
>>
>>> William A. Rowe Jr. wrote:
>>>
On 5/7/2011 7:16 AM, Justin Schoeman wrote:
> It does not matter which of these I try, openssl alwa
