Hi, everybody,
there is a new release of M2Crypto, most complete Python bindings
for OpenSSL (from 1.0.1e to 1.1.1), supporting both Python 2 (2.6
and 2.7) and Python 3 (from 3.4 upwards).
This is mostly bugfix release, including:
- support for OpenSSL 1.1.1
- Fixes for Windows builds
-
Hi, everybody,
this is just a bugfix release. Marcus Huewe stepped up and
produced a lot of smaller bugfixes while working on
https://gitlab.com/m2crypto/m2crypto/merge_requests/188 (which
itself has not been finished yet for this release).
Also, we finally got rid off some remaining old-style
On 2018-04-17, 22:36 GMT, Rob Marshall wrote:
> The OS is SLES 10 SP3 and there are currently close to 80
> binaries that appear to use libssl.so.0.9.8.
Whoever decided this platform is a good idea, was in my opinion
wrong. https://en.wikipedia.org/wiki/SUSE_Linux_Enterprise tells
me that a)
Hi, everybody,
just on the heels of 0.28.* with Python 3 compatibility with
0.29.0 resolving another heavy problem. This time we have renewed
compatibility with Windows (all tests pass on Win32 and Win64 on
all supported combinations of versions of OpenSSL and Python).
The problem I have and I
Hi, everybody,
after a way too long time I have finally version of M2Crypto
working BOTH with Python 2.6 and 2.7 and with versions of Python
from 3.3 up.
Certainly the biggest feature of this release that we are finally
compatible both with py2k (Python 2.6 and 2.7) and py3k (from
Python 3.3
On 2017-10-11, 12:11 GMT, Blumenthal, Uri - 0553 - MITLL wrote:
> Unfortunately, not quite. Being pip-installable means to the
> majority of users that the package in question can be
> installed via, e.g.,
>
>pip install M2Crypto
I understand that, my question was whether you know how to
On 2017-10-11, 11:35 GMT, Blumenthal, Uri - 0553 - MITLL wrote:
> And it is not installable via PIP, though to me being placed
> on pypi site suggested that it should be (that's how I tried
> to install it).
What’s needed for package to be pip installable? I would think
that if
python
do you actually have err.h? Manually settings CFLAGS and
LDFLAGS should be followed by seutp.py, it can help as
a workaround, but my dream is that plain settings of --openssl
parameter should be sufficient.
Feel free to continue here, on on the issue tracker.
Best,
Matěj Cepl
--
http://matej
M2Crypto is the most complete Python wrapper for OpenSSL
featuring RSA, DSA, DH, EC, HMACs, message digests, symmetric
ciphers; SSL functionality to implement clients and servers;
HTTPS extensions to Python’s httplib, urllib, and xmlrpclib;
unforgeable HMAC’ing AuthCookies for web session
One more bugfix release, fixing one silly FTBFS presenting itself on
systems with OpenSSL 1.1.0 and LibreSSL (if anybody can provide some
testing experience with LibreSSL and file bugs at
https://gitlab.com/m2crypto/m2crypto/issues it would be very helpful).
I am sorry,
Matěj
--
On 21/09/17 00:26, Matej Cepl wrote:
> after a way too long time I have another version of M2Crypto. Despite
> the deceptively minor version number (0.26.2; it is mistake, it has all
> right to be called 0.27.0, but the release is already on PyPI, sorry)
> this was a lot of work.
Oh well, so I
On 2017-09-12, 19:33 GMT, Dr. Stephen Henson wrote:
> Yes *_seq_unpack() is no longer in 1.1. What happens is that
> code above it generates a function d2i_SEQ_CERT() which does
> the same as ASN1_seq_unpack() for a certificate.
>
> So something like this should work:
>
> const unsigned char
Hi,
I am working on porting M2Crypto to OpenSSL 1.1.* API (in branch
https://gitlab.com/mcepl/m2crypto/commits/openssl-1.1.0 ) and I
got lost in STACK_OF structures.
Simplified function I have troubles with is (the real stuff with
all Python2/Python3 shims is https://is.gd/Nbq3Qp ; the similar
objects derived from BIO.BIO now could work as context managers
- Switch setup.py to setuptools
0.22.5 - 2015-10-13
---
- Add forgoteen SWIG/*.h among distributed files.
0.22.4 - 2015-10-13
---
- Matěj Cepl takes over leadership of the upstream maintenance
- Fedora/RHEL
On 2016-05-26, 16:33 GMT, R-D intern wrote:
> I have implemented ssl for my internal server that listens
> over a private ip. Can anyone suggest how can I test my
> ssl_server? For eg. Qualys test shows the amount of ssl
> implementation of a server listening over public ip and even
> checks
On 2016-04-21, 20:50 GMT, Lei Kong wrote:
> Can SSL library be used in Linux kernel mode?
A bit of problem is that the OpenSSL’s license is incompatible
with GPLv2.
Matěj
--
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC
Hi,
I am trying to make M2Crypto build on Windows again
(https://gitlab.com/m2crypto/m2crypto/merge_requests/26). I have
replaced by POSIX's poll by WSAPoll( I know about
https://daniel.haxx.se/blog/2012/10/10/wsapoll-is-broken/ but we
don't play with the error values, which is a mistake, I know,
On 2016-04-06, 12:16 GMT, Tomasz Chmielewski wrote:
> error: File not found by glob:
> /root/rpmbuild/BUILDROOT/openssl-1.0.2g-1.x86_64/usr/lib/*.so*
This is something really really weird. x86_64 package should
never ever write anything to /usr/lib/ , but only to /usr/lib64.
You have to have
Hi,
I am the crazy guy who decided to continue in maintenance of
M2Crypto when everybody else wisely (?) left the ship.
Unfortunately (for M2Crypto), I am a Linux guy, so while I have
finally gave up and installed Windows X in VM, I am really lost
in the Windows APIs and we have currently
On 2015-11-27, 09:28 GMT, Tim Hudson wrote:
> http://www.mail-archive.com/openssl-dev@openssl.org/msg28042.html
That’s
http://article.gmane.org/gmane.comp.encryption.openssl.devel/17997/
for those afflicted with gmane’s mangling of anything looking
like an email address.
Matěj
--
20 matches
Mail list logo
