search for: 0x20000000l

Displaying 13 results from an estimated 13 matches for "0x20000000l".

Did you mean: 0x20000000
2016 Nov 02
3
v2.2.26.0 released
...hink catches them all where needed. Note the word think. It certainly appears to be working anyway with it. On 11/02/2016 04:07 AM, Aki Tuomi wrote: > After doing some testing by myself, I noticed that libressl, for some > unknown reason, defines > > #define OPENSSL_VERSION_NUMBER 0x20000000L > > No idea why they decided to advertise that they are OpenSSL v2.0.0. A > local fix, if you need one, is to use > > #if OPENSSL_VERSION_NUMBER == 0x20000000L > #define OPENSSL_VERSION_NUMBER 0x1000100L > #endif > > in dcrypt-openssl.c after includes. > > Aki >...
2016 Nov 02
2
v2.2.26.0 released
...>> It certainly appears to be working anyway with it. >> >> On 11/02/2016 04:07 AM, Aki Tuomi wrote: >>> After doing some testing by myself, I noticed that libressl, for some >>> unknown reason, defines >>> >>> #define OPENSSL_VERSION_NUMBER 0x20000000L >>> >>> No idea why they decided to advertise that they are OpenSSL v2.0.0. A >>> local fix, if you need one, is to use >>> >>> #if OPENSSL_VERSION_NUMBER == 0x20000000L >>> #define OPENSSL_VERSION_NUMBER 0x1000100L >>> #endif >>&...
2016 Nov 02
2
v2.2.26.0 released
...y appears to be working anyway with it. >>> >>> On 11/02/2016 04:07 AM, Aki Tuomi wrote: >>>> After doing some testing by myself, I noticed that libressl, for some >>>> unknown reason, defines >>>> >>>> #define OPENSSL_VERSION_NUMBER 0x20000000L >>>> >>>> No idea why they decided to advertise that they are OpenSSL v2.0.0. A >>>> local fix, if you need one, is to use >>>> >>>> #if OPENSSL_VERSION_NUMBER == 0x20000000L >>>> #define OPENSSL_VERSION_NUMBER 0x1000100L >&...
2016 Nov 02
2
v2.2.26.0 released
Hi! Those are used if #if OPENSSL_VERSION_NUMBER >= 0x10100000L So (your) libressl is providing this define. We compile our code using GCC and CLANG regularly, with OpenSSL v1.0.x which is the currently officially supported one. Aki On 02.11.2016 12:34, Ruga wrote: > dovecot 2.2.26.0 uses the following functions, which are not available on libressl 2.4.3: > > HMAC_CTX_new >
2016 Nov 02
0
v2.2.26.0 released
After doing some testing by myself, I noticed that libressl, for some unknown reason, defines #define OPENSSL_VERSION_NUMBER 0x20000000L No idea why they decided to advertise that they are OpenSSL v2.0.0. A local fix, if you need one, is to use #if OPENSSL_VERSION_NUMBER == 0x20000000L #define OPENSSL_VERSION_NUMBER 0x1000100L #endif in dcrypt-openssl.c after includes. Aki On 02.11.2016 12:39, Aki Tuomi wrote: > Hi! > &...
2016 Nov 02
2
v2.2.26.0 released
...gt;> On 11/02/2016 04:07 AM, Aki Tuomi wrote: >>>>>> After doing some testing by myself, I noticed that libressl, for >>>>>> some >>>>>> unknown reason, defines >>>>>> >>>>>> #define OPENSSL_VERSION_NUMBER 0x20000000L >>>>>> >>>>>> No idea why they decided to advertise that they are OpenSSL >>>>>> v2.0.0. A >>>>>> local fix, if you need one, is to use >>>>>> >>>>>> #if OPENSSL_VERSION_NUMBER == 0x20000000...
2016 Nov 02
0
v2.2.26.0 released
...d. Note the word think. > > It certainly appears to be working anyway with it. > > On 11/02/2016 04:07 AM, Aki Tuomi wrote: >> After doing some testing by myself, I noticed that libressl, for some >> unknown reason, defines >> >> #define OPENSSL_VERSION_NUMBER 0x20000000L >> >> No idea why they decided to advertise that they are OpenSSL v2.0.0. A >> local fix, if you need one, is to use >> >> #if OPENSSL_VERSION_NUMBER == 0x20000000L >> #define OPENSSL_VERSION_NUMBER 0x1000100L >> #endif >> >> in dcrypt-openssl.c...
2016 Nov 02
0
v2.2.26.0 released
...ppears to be working anyway with it. >>> >>> On 11/02/2016 04:07 AM, Aki Tuomi wrote: >>>> After doing some testing by myself, I noticed that libressl, for some >>>> unknown reason, defines >>>> >>>> #define OPENSSL_VERSION_NUMBER 0x20000000L >>>> >>>> No idea why they decided to advertise that they are OpenSSL v2.0.0. A >>>> local fix, if you need one, is to use >>>> >>>> #if OPENSSL_VERSION_NUMBER == 0x20000000L >>>> #define OPENSSL_VERSION_NUMBER 0x1000100L >&...
2016 Nov 02
0
v2.2.26.0 released
...anyway with it. >>>> >>>> On 11/02/2016 04:07 AM, Aki Tuomi wrote: >>>>> After doing some testing by myself, I noticed that libressl, for some >>>>> unknown reason, defines >>>>> >>>>> #define OPENSSL_VERSION_NUMBER 0x20000000L >>>>> >>>>> No idea why they decided to advertise that they are OpenSSL v2.0.0. A >>>>> local fix, if you need one, is to use >>>>> >>>>> #if OPENSSL_VERSION_NUMBER == 0x20000000L >>>>> #define OPENSSL_VERSION...
2016 Dec 04
2
v2.2.27 released --- libressl
>openssl version Libressl 2.4.4 Patch for dovecot: perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER < 0x10100000L\s*)$/$1 || defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-dcrypt/dcrypt-openssl.c; perl -i -ple 's/^(#if OPENSSL_VERSION_NUMBER < 0x10100000L\s*)$/$1 || defined (LIBRESSL_VERSION_NUMBER)/' ./src/lib-ssl-iostream/dovecot-openssl-common.c; perl -i -ple 's/^(#if
2016 Dec 06
0
v2.2.27 released --- libressl
Results from the application of the following patch from Aki. perl -i -ple 's|^(\s*#include <openssl/opensslv.h>\s*)$|$1\n\t#if OPENSSL_VERSION_NUMBER == 0x20000000L\n\t#define OPENSSL_VERSION_NUMBER 0x10001000L\n\t#endif|' configure.ac; -------------- next part -------------- A non-text attachment was scrubbed... Name: compiler-stderr.log Type: application/octet-stream Size: 16045 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/atta...
2006 Sep 26
15
RE: Individual passwords for guest VNC servers ?
> Thanks all point about security, I''ll do as follows. > I thought that the point was the following two. > > > 1. Storage place of encrypted password > Should I store it in /etc/xen/passwd ? > Or, should I wait for DB of Xen that will be released in > the future? The xend life cycle management patches were posted by Alistair a couple of months back.
2016 Nov 02
0
v2.2.26.0 released
...y keep this promise, then we should have no worries about things > breaking up. Diff below is what I've added to OpenBSD ports. The libressl API is not cast in stone, there's a possibility some functions from newer OpenSSL might be added - in fact we already have some like TLS_method. 0x20000000L was specifically chosen to not match up with anything OpenSSL had used because they aren't directly comparable. In general I think the best approach would be for feature checks, e.g. in autoconf. (I wish there was some common m4 file shared between projects that people could use for this..) In...