[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2021-10-06 Thread Bryce Harrington
[Xenial has reached its end of standard support.]

** Changed in: bind9 (Ubuntu Xenial)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2018-01-12 Thread ChristianEhrhardt
Hi Brian,
these versions are actually already in Artful and Bionic.
Given the time you opened this you found that on Xenial I'll add a task for an 
SRU.

@Andreas - you look at bind fixes every now and then - how about to
include this on your next run?

** Also affects: bind9 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: bind9 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: bind9 (Ubuntu Xenial)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2018-01-11 Thread Brian Menges
Will this be fixed any time soon?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2017-11-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bind9 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2017-11-28 Thread Brian Menges
I can confirm that the following debian packages resolve the issue:

bind9_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
bind9utils_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libbind9-140_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libdns162_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libgssapi-krb5-2_1.15-1+deb9u1_amd64.deb
libisc160_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libisccc140_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libisccfg140_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libk5crypto3_1.15-1+deb9u1_amd64.deb
libkrb5-3_1.15-1+deb9u1_amd64.deb
libkrb5support0_1.15-1+deb9u1_amd64.deb
liblwres141_9.10.3.dfsg.P4-12.3+deb9u3_amd64.deb
libssl1.0.2_1.0.2l-2+deb9u1_amd64.deb

If we could get bind9 and dependencies rebuilt with the necessary patch
(from the bug, a 1-liner) that'd be splendid so that we can return to a
safe chroot bind9 scenario

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2017-11-28 Thread Brian Menges
Per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820974#86 , Debian
has fixed this. Can we please import this package to get this resolved?
While this may be thought of as a non-standard configuration this is a
critical security issue that is now solved upstream. Could we please get
this update pushed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2017-02-07 Thread Bug Watch Updater
** Changed in: bind9 (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2016-10-05 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Since this bug affects a non-default configuration of bind, there are
alternatives (such as AppArmor and running in a container) and OpenVZ is
not part of Ubuntu, I'm setting the importance of this bug to Low. I
don't expect anyone on the Ubuntu Server Team to work on this bug, but
if someone else wants to provide a fix, please do.

** Changed in: bind9 (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2016-10-04 Thread Alexander Radev
** Also affects: bind
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1630025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1630025] Re: Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

2016-10-03 Thread Bug Watch Updater
** Changed in: bind9 (Debian)
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630025

Title:
  Fails running In chroot with "ENGINE_by_id failed (crypto failure)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1630025/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs