-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-13 15:03:39 -0400, Brett Glass wrote:
> Will port also be MFCed to 9-RELENG and 9.1-RELEASE? Do not want
> to have to go to -CURRENT to get latest OpenSSL.
Sorry, we have no plan to MFC this to stable branches because of API
and feature cha
Will port also be MFCed to 9-RELENG and 9.1-RELEASE? Do not want to
have to go to -CURRENT to get latest OpenSSL.
--Brett Glass
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-13 04:00:14 -0400, Konstantin Belousov wrote:
> How did the asm files were generated (I am sure they are generated)
> ?
Yes, they are all re-generated. Mostly, it is described in
FREEBSD-upgrade file:
http://svnweb.freebsd.org/base/vendor
On 07/13/2012 08:52 AM, Jung-uk Kim wrote:
> On 2012-07-13 05:55:04 -0400, Doug Barton wrote:
>> On 07/12/2012 05:03 PM, Jung-uk Kim wrote:
>>> FYI, OpenSSL 1.0.1c import is complete now. Please let me know
>>> if you have any problem.
>
>> Sorry if I missed it, but did you bump OSVERSION for thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-13 05:55:04 -0400, Doug Barton wrote:
> On 07/12/2012 05:03 PM, Jung-uk Kim wrote:
>> FYI, OpenSSL 1.0.1c import is complete now. Please let me know
>> if you have any problem.
>
> Sorry if I missed it, but did you bump OSVERSION for this
On 07/12/2012 05:03 PM, Jung-uk Kim wrote:
> FYI, OpenSSL 1.0.1c import is complete now. Please let me know if you
> have any problem.
Sorry if I missed it, but did you bump OSVERSION for this change? If
not, could you? It would be helpful for dealing with ports stuff,
especially USE_OPENSSL.
Do
Hello, Lev.
You wrote 13 июля 2012 г., 12:29:03:
JuK>> FYI, OpenSSL 1.0.1c import is complete now. Please let me know if you
JuK>> have any problem.
LS> No ports with "USE_OPENSSL=yes" could be built now :( Ports system
LS> complains about not-installed base OpenSSL.
Sorry for noise, it is
Hello, Jung-uk.
You wrote 13 июля 2012 г., 4:03:09:
>> Therefore, all binaries depending on these need to be recompiled.
>> Also, you may have to merge your /etc/ssl/openssl.conf changes.
JuK> FYI, OpenSSL 1.0.1c import is complete now. Please let me know if you
JuK> have any problem.
No por
On Thu, Jul 12, 2012 at 08:03:09PM -0400, Jung-uk Kim wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2012-07-12 14:04:58 -0400, Jung-uk Kim wrote:
> > OpenSSL 1.0.1c will be merged to head today. There will be
> > several important changes to note.
> >
> > - Several crypto/engin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-12 14:04:58 -0400, Jung-uk Kim wrote:
> OpenSSL 1.0.1c will be merged to head today. There will be
> several important changes to note.
>
> - Several crypto/engine modules will be added or enabled by default
> to closely match OpenSSL defa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-12 14:04:58 -0400, Jung-uk Kim wrote:
> - Several crypto/engine modules will be added or enabled by default
> to closely match OpenSSL default, e.g., Camellia (crypto), SEED
> (crypto), CHIL (engine), GOST (engine), etc.
Actually, CHIL is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL 1.0.1c will be merged to head today. There will be several
important changes to note.
- - Several crypto/engine modules will be added or enabled by default to
closely match OpenSSL default, e.g., Camellia (crypto), SEED (crypto),
CHIL (engine
12 matches
Mail list logo
