I've been able to test this error by creating a bogus symlink in
/etc/ssl/certs and I committed a patch that removes any orphan symlinks,
prior to running `openssl rehash`.
https://salsa.debian.org/debian/ca-certificates/commit/cfe7064cb707ed2e8ac587877c1153029d46dc28
--
Kind regards,
Michael.
Hi Michael,
Michael Shuler wrote:
> [x] I intend to find the time between work, family, and multiple other
> projects to attempt to reliably reproduce the problem, in order to
> intelligently answer the above.
Much appreciated, thanks!
In the hope that it helps you to track down this iss
On 06/20/2018 04:33 PM, Sebastian Andrzej Siewior wrote:
On 2018-06-13 08:19:32 [+0200], To Axel Beckert wrote:
I asked upstream what they thing about ignoring these errors because the
perl script does so. On the other hand what about cleaning up these
dangling symlinks?
ca-certificate maintai
On 2018-06-13 08:19:32 [+0200], To Axel Beckert wrote:
> I asked upstream what they thing about ignoring these errors because the
> perl script does so. On the other hand what about cleaning up these
> dangling symlinks?
ca-certificate maintainers: what do we do here?
[ ] we intend to figure out
On 2018-06-13 00:10:57 [+0200], Axel Beckert wrote:
> Hi Sebastian,
Hi Axel,
> Sebastian Andrzej Siewior wrote:
> > > I don't think so unless a future upload of OpenSSL to unstable fixes
> > > this. The recent one to unstable didn't.
> >
> > forwarded https://github.com/openssl/openssl/issues/647
Hi Sebastian,
Sebastian Andrzej Siewior wrote:
> > I don't think so unless a future upload of OpenSSL to unstable fixes
> > this. The recent one to unstable didn't.
>
> forwarded https://github.com/openssl/openssl/issues/6475
>
> Just a little question: The missing certificates:
> |rehash: error
On 2018-06-12 22:29:42 [+0200], Axel Beckert wrote:
> Shall I try the version from Experimental, too?
no.
> > (Should some Breaks be added, Depends made stricter?)
>
> I don't think so unless a future upload of OpenSSL to unstable fixes
> this. The recent one to unstable didn't.
forwarded https:
Hi Kurt,
Kurt Roeckx wrote:
> > > Given that this openssl update is now in testing, should we close or at
> > > least downgrade this bug so ca-certificates can migrate?
> >
> > I just unhold ca-certificates 20170717 and upgraded it to 20180409 on
> > one of my affected machines (the i386 one) and
On Tue, Jun 12, 2018 at 09:57:56PM +0200, Axel Beckert wrote:
> Hi,
>
> Thijs Kinkhorst wrote:
> > >> I've read about this bug (and the other one) on d-devel. I uploaded
> > >> recently a new version of openssl to unstable (1.1.0h-3)which changes
> > >> the exit code of "openssl rehash" to zero in
Hi,
Thijs Kinkhorst wrote:
> >> I've read about this bug (and the other one) on d-devel. I uploaded
> >> recently a new version of openssl to unstable (1.1.0h-3)which changes
> >> the exit code of "openssl rehash" to zero in case of a duplicate or if a
> >> certificate can no be open.
> >> I left
On Wed, May 30, 2018 20:22, Michael Shuler wrote:
> On 05/30/2018 12:46 PM, Sebastian Andrzej Siewior wrote:
>>
>> I've read about this bug (and the other one) on d-devel. I uploaded
>> recently a new version of openssl to unstable (1.1.0h-3)which changes
>> the exit code of "openssl rehash" to zer
On 05/30/2018 12:46 PM, Sebastian Andrzej Siewior wrote:
I've read about this bug (and the other one) on d-devel. I uploaded
recently a new version of openssl to unstable (1.1.0h-3)which changes
the exit code of "openssl rehash" to zero in case of a duplicate or if a
certificate can no be open.
On 2018-04-22 16:55:21 [+0200], Axel Beckert wrote:
> Hi Michael,
Hi,
> Michael Shuler wrote:
> > Thanks for the details. #895473 reported a similar error on locally
> > installed CA certificates, which I think may be related.
>
> That other bug report indeed looks similar albeit not identical.
…
Hi Michael,
Michael Shuler wrote:
> Thanks for the details. #895473 reported a similar error on locally
> installed CA certificates, which I think may be related.
That other bug report indeed looks similar albeit not identical.
> I've tried a number of upgrades from a March 29 unstable chroot, a
Thanks for the details. #895473 reported a similar error on locally
installed CA certificates, which I think may be related.
Each of the list of `rehash: skipping .. cannot open file` in your
errors appears to be on CAs that were removed in the package during this
update, so somewhere we have a pr
Hi,
Axel Beckert wrote:
> On other sid installations (including architectures amd64, i386 and
> armhf), the upgrade worked fine, […]
Correction: It failed on one i386 sid machine, too:
Updating certificates in /etc/ssl/certs...
W: /usr/share/ca-certificates/mozilla/GeoTrust_Global_CA_2.crt not f
Package: ca-certificates
Version: 20180409
Severity: serious
Upgrading ca-certificates from 20170717 to 20180409 fails for me as
follows on one machine:
Before unpacking, I have been shown this dialog, which I acknowledged
by pressing enter:
┌┤ ca-certificates c
17 matches
Mail list logo
