Re: ahci-timeout regression in beta3

Bezüglich Harry Schmalzbauer's Nachricht vom 28.02.2016 20:55 (localtime): > Hello, > > I have a remote machine with a probably defective ODD, but until r294989 > (from Jan 28th) I could boot with just these warnings: > (cd1:ahcich1:0:0:0): READ(10). CDB: 28 00 00 38 85 e0 00 00 01 00 >

Re: svn commit: r295367 - in stable/10: crypto/openssh crypto/openssh/contrib crypto/openssh/contrib/caldera crypto/openssh/contrib/cygwin crypto/openssh/contrib/redhat crypto/openssh/contrib/suse cry

Hi, I noticed on a server that I updated on Friday that incorporates r295367, some lightweight clients that were using aes128-cbc are now failing to connect. Is this a planned change ? If so, perhaps a heads up in UPDATING ? e.g. from an older client ssh -c aes128-cbc

Re: Problem with /usr/lib/libcrypt.a when building perl/python with libressl

On Mon, Feb 29, 2016 at 4:05 AM, Dewayne Geraghty wrote: > I understand the value of fPIC for shareable libraries but I'm a little > confused as to why libcrypt.a requires -fPIC; which BTW does enable both > python, perl and others to build cleanly. > Both perl and

Congratulations you’ve won our exclusive free currency Trader Guide

Join the world's largest and most exciting trading market in the world - with the perfect package*: Free Pro Trader EBook $5000 Demo Account Up to 25% Bonus** Personal 1 on 1 Training 14 Hours of Video Lessons 24/6 Customer

Problem with /usr/lib/libcrypt.a when building perl/python with libressl

I'm trying to rebuild my local ports tree using libressl. Unfortunately the linker is advising that I should build /usr/lib/libcrypt.a with -fPIC. As its a security-related module, I would appreciate advise as to whether this will/may cause a security issue? The message, during the link phase,