[Bug 1725250] Comment bridged from LTC Bugzilla

2018-07-02 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2018-07-02 05:10 EDT--- IBM Bugzilla status -> closed, Fix Released for Artful, Bionic, Cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1725250] Comment bridged from LTC Bugzilla

2018-06-11 Thread Dimitri John Ledkov
On 18 May 2018 at 15:51, bugproxy wrote: > --- Comment From ebarre...@br.ibm.com 2018-05-18 10:41 EDT--- > Hi Harald, > > I agree that we should investigate this, so let's keep this discussion > going outside here. > > @Dimitri, just out of curiosity, that Xfe ticket that you mentioned is

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-18 Thread bugproxy
--- Comment From ebarre...@br.ibm.com 2018-05-18 10:41 EDT--- Hi Harald, I agree that we should investigate this, so let's keep this discussion going outside here. @Dimitri, just out of curiosity, that Xfe ticket that you mentioned is from 2010. So the "-Bsymbolic-functions" is on Ubuntu

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-18 Thread bugproxy
--- Comment From fre...@de.ibm.com 2018-05-18 09:33 EDT--- Hello Dimitri clearly this bug is not the right place to track a re-evaluation and possible re-design of opencryptoki. So far I understand this option it prevents some kind of attacks with preloaded shard libs which provide some

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-18 Thread bugproxy
--- Comment From fre...@de.ibm.com 2018-05-18 03:59 EDT--- So did I get it right ? It was just the -Wl,-Bsymbolic-functions linker option ? Even if this is fixed for now, we should spend some time on finding out why this linker option breaks the opencryptoki build. The man page says:

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-17 Thread bugproxy
--- Comment From ebarre...@br.ibm.com 2018-05-17 09:40 EDT--- Hi Dimitri, Here worked as well on my tests. Thanks for fixing it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725250 Title:

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-16 Thread bugproxy
--- Comment From ebarre...@br.ibm.com 2018-05-16 13:14 EDT--- Hi Dimitri, No, libep11 is not the problem and the message that you are seeing on gdb is not the main reason. This error message: pkcsconf[187270]: ep11_specific.c ep11tok_init: Error loading shared library 'libep11.so'

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-16 Thread bugproxy
--- Comment From christian.r...@de.ibm.com 2018-05-16 12:13 EDT--- To help in narrowing down In a next step I installed the libraries for CCA (csulcca_6.0.9-11_s390x.deb) and EP11 (libep11_1.3.2-1_s390x.deb) which are distributed by IBM. The pacakge-provided

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-16 Thread bugproxy
--- Comment From christian.r...@de.ibm.com 2018-05-16 11:43 EDT--- We reproduced the problem on a zVM Guest UBUNTU 18.04 ( 4.15.0-20-generic ) instance running on IBM Z 14 machine (IBM Type: 3906 Model: 703 M03) using opencryptoki version 3.9.0+dfsg-0ubuntu1. ~# lscpu

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-16 Thread bugproxy
--- Comment From ebarre...@br.ibm.com 2018-05-16 10:20 EDT--- Hi Frank, As we mentioned in the description, if you manually build and install opencryptoki, everything works. So, it is clear that is something wrong in the .deb package. Could it be possible for you guys to generate a new

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-14 Thread bugproxy
--- Comment From ebarre...@br.ibm.com 2018-05-14 12:37 EDT--- Hi Frank, I've found something interesting. On Ubuntu 18.04, if you comment ep11 (slot 4) from the /etc/opencryptoki.conf, and restart pkcsslotd, then pkcsconf -t works. But even commenting ep11 from the configuration file,

[Bug 1725250] Comment bridged from LTC Bugzilla

2018-05-14 Thread bugproxy
--- Comment From ebarre...@br.ibm.com 2018-05-14 12:01 EDT--- (In reply to comment #21) > bisect required from 3.7.0 to 3.8.1 to identify when the fix got introduced. Hi Frank, Do we have any update on this issue? It just came to my knowledge that it is also happening on Ubuntu 18.04.

[Bug 1725250] Comment bridged from LTC Bugzilla

2017-10-20 Thread bugproxy
--- Comment From christian.r...@de.ibm.com 2017-10-20 09:58 EDT--- Hello Frank, you might want to run 'id' to see if your user is member of the pkcs11 group. Further ensure the pkcsslotd is started. Thanks, Christian -- You received this bug notification because you are a member of