Bug#929903: openssl: m2crypto test case regression

2019-06-08 Thread Matěj Cepl
Sebastian Andrzej Siewior píše v Út 04. 06. 2019 v 23:10 +0200:
> It did not if I understand the python correctly:
> >with self.assertRaises(RSA.RSAError):
> >priv.private_decrypt(ctxt, RSA.sslv23_padding)
> 
> you expect that `priv.private_decrypt()' raised an RSA.RSAError
> exception which it did before c (due to that bug) and did not since c.

I believe M2Crypto 0.35.1 is what you are looking for. Thank you
very much for finding the problem.

Best,

Matěj

-- 
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
La vita è una combinazione di magia e pasta.
  -- Federico Fellini


signature.asc
Description: This is a digitally signed message part


Bug#929903: openssl: m2crypto test case regression

2019-06-04 Thread Matěj Cepl
Sebastian Andrzej Siewior píše v Út 04. 06. 2019 v 14:15 +0200:
> Let me ping upstream: Matěj, could you please take a look at
>   https://bugs.debian.org/929903

Also, the upstream bug for this is 
https://gitlab.com/m2crypto/m2crypto/issues/258

Best,

Matěj

-- 
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
- Do you think of yourself as a Christian artist?
- I'm an artist who is a Christian. I'm not a Christian artist.
  -- Johny Cash
 in his last interview


signature.asc
Description: This is a digitally signed message part


Bug#929903: openssl: m2crypto test case regression

2019-06-04 Thread Matěj Cepl
Sebastian Andrzej Siewior píše v Út 04. 06. 2019 v 14:15 +0200:
> Let me ping upstream: Matěj, could you please take a look at
>   https://bugs.debian.org/929903
> 
> and check if it is okay the test no longer fails or if openssl suddenly
> eats up the error code. Afterall:

OK, I have this commit now in the master 
https://gitlab.com/m2crypto/m2crypto/commit/f287d7145b5f but I am
still not certain that sslv23_padding and especially no_padding
should lead to error, shouldn't it?

Why did the test passed before otherwise?

Best,

Matěj

> --- tests/test_rsa.py   2019-06-03 21:16:33.84000 +
> +++ tests/test_rsa.py.new   2019-06-04 12:14:21.16800 +
> @@ -124,10 +124,10 @@
>  
>  # sslv23_padding
>  ctxt = priv.public_encrypt(self.data, RSA.sslv23_padding)
> -with self.assertRaises(RSA.RSAError):
> -priv.private_decrypt(ctxt, RSA.sslv23_padding)
> -with self.assertRaises(RSA.RSAError):
> -priv.private_decrypt(ctxt, RSA.sslv23_padding)
> +ptxt = priv.private_decrypt(ctxt, RSA.sslv23_padding)
> +self.assertEqual(ptxt, self.data)
> +ptxt = priv.private_decrypt(ctxt, RSA.sslv23_padding)
> +self.assertEqual(ptxt, self.data)
>  
>  # no_padding
>  with self.assertRaises(RSA.RSAError):
> 
> passes now and the result is `equal'.


signature.asc
Description: This is a digitally signed message part


Bug#923446: m2crypto: autopkgtest with new version of openssl: Connection refused

2019-03-07 Thread Matěj Cepl
Sebastian Andrzej Siewior píše v So 02. 03. 2019 v 17:16 +0100:
> The thing is that m2ctypto uses TLS1.3 cipher but uses the -cipher
> option instead of -ciphersuites which is for TLS1.3:
> > $ openssl s_server --help 2>&1 |grep -- -cipher
> > -cipher valSpecify TLSv1.2 and below cipher list to be used
> > -ciphersuites val  Specify TLSv1.3 ciphersuites to be used
> 
> The patch attached against m2crypto fixes the testsuite issue.

Thank you, merged in https://gitlab.com/m2crypto/m2crypto/merge_requests/224 

Matěj
-- 
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
I would like to die sleeping, like my father — rather than
screaming and helpless, like his passengers.


signature.asc
Description: This is a digitally signed message part


Bug#643680: Could I ask for a reproducer?

2017-10-06 Thread Matěj Cepl
Hi,

this is your happy upstream maintainer of M2Crypto. I tried to reproduce
this bug here, but I have failed so far. Could you be so kind and and
provide some complete standalone testing script together with all data
files (certificates, etc.) needed for the reproduction, please?

If I can reproduce the problem, I will gladly try to fix it.

Thank you for reporting this,

Matěj Cepl



signature.asc
Description: OpenPGP digital signature


Bug#631806: This is almost certainly obsolete

2017-10-06 Thread Matěj Cepl
I cannot reproduce this even with python-m2crypto in
Debian/stretch (that's 0.24.0 from 2016-03-21). The last version
where I could reproduce it is on my RHEL-7 (0.21.1 from 2011-01-
15).

If you can reproduce the bug with version of M2Crypto more recent
than the last year, I would be interested in the bug report
upstream (https://gitlab.com/m2crypto/m2crypto/issues/new ).

Thank you,

Matěj



Bug#717675: This has been fixed upstream

2017-10-06 Thread Matěj Cepl
This has been already fixed by the upstream commit 79032181 in
the release 0.26.0 from 2017-03-25.

Happy hacking!

Matěj

signature.asc
Description: This is a digitally signed message part


Bug#859225: M2Crypto na OpenSSL 1.1.0

2017-10-06 Thread Matěj Cepl
Just to say, that M2Crypto since 0.26.2 (current release is
0.27.0) officially supports OpenSSL 1.1.0 API, no compat-
libraries are needed anymore.

Best,

Matěj Cepl
(upstream maintainer of M2Crypto)

signature.asc
Description: This is a digitally signed message part


Bug#774486: pyg: There is now new upstream

2015-01-03 Thread Matěj Cepl
Package: pyg
Version: 0.9.7+b2
Severity: important

Dear Maintainer,

I have uploaded a new (hopefully more sane) version of the package to 
PIP and I intent to maintain it there.

The URL is https://pypi.python.org/pypi/pygn (unfortunately, pyg name 
has been already taken by a now dead package).

-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pyg depends on:
ii  libc6   2.13-38+deb7u6
ii  python  2.7.3-4+deb7u1
ii  python-support  1.0.15

pyg recommends no packages.

Versions of packages pyg suggests:
ii  exim4-daemon-light [mail-transport-agent]  4.80-7+deb7u1
pn  news-transport-system  none
ii  procmail   3.22-20+deb7u1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#641925: vimoutliner: New upstreams available

2014-12-13 Thread Matěj Cepl
Package: vim-vimoutliner
Version: 0.3.4+pristine-9.1
Followup-For: Bug #641925

Dear Maintainer,

there is actually 0.3.6 now upstream. Also, what do you mean by
the binary stuff?

Also, please, change the upstream URL in description to either
https://github.com/vimoutliner/vimoutliner or to http://vimoutliner.cepl.eu

-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vim-vimoutliner depends on:
ii  libpalm-perl1:1.012-1
ii  libxml-writer-perl  0.615-1
ii  perl5.14.2-21+deb7u2
ii  python  2.7.3-4+deb7u1
ii  vim 2:7.3.547-7
ii  vim-nox [vim]   2:7.3.547-7

Versions of packages vim-vimoutliner recommends:
ii  vim-addon-manager  0.5.2

vim-vimoutliner suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#641925: vimoutliner: New upstreams available

2014-12-13 Thread Matěj Cepl
Package: vim-vimoutliner
Version: 0.3.4+pristine-9.1
Followup-For: Bug #641925

Dear Maintainer,

there is actually 0.3.6 now upstream. Also, what do you mean by
the binary stuff?

Also, please, change the upstream URL in description to either
https://github.com/vimoutliner/vimoutliner or to http://vimoutliner.cepl.eu

-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vim-vimoutliner depends on:
ii  libpalm-perl1:1.012-1
ii  libxml-writer-perl  0.615-1
ii  perl5.14.2-21+deb7u2
ii  python  2.7.3-4+deb7u1
ii  vim 2:7.3.547-7
ii  vim-nox [vim]   2:7.3.547-7

Versions of packages vim-vimoutliner recommends:
ii  vim-addon-manager  0.5.2

vim-vimoutliner suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#557432: We have it building!

2014-07-01 Thread Matěj Cepl
After spending some time fixing builds on Fedora, I took a view over the
fence, and found this bug. Maybe trying our patches (at
http://pkgs.fedoraproject.org/cgit/ucblogo.git/tree/ ) could help?

Best,

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mc...@ceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC

My life has been full of terrible misfortunes most of which never
happened.
-- Michel de Montaigne



signature.asc
Description: OpenPGP digital signature


Bug#439440: Close bug

2013-09-08 Thread Matěj Cepl
It seems to me that the maintainer forgot to close this bug. Patch has
been already applied, it seems.

Best,

Matěj Cepl



signature.asc
Description: OpenPGP digital signature


Bug#464531: There is new upstream

2008-11-30 Thread Matěj Cepl
Oh well,

I hoped that Debian will be (as usual) source of already made
pacages even in this case, but apparently note. So, OK just to
note that there is now new upstream for jingle/trang/etc. which
should be also upgraded to work with the latest Java.

http://code.google.com/p/jing-trang/


Matěj Cepl




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]