Control: severity -1 serious Hi,
I believe this is a serious bug, since it affects the most common way to deploy bind9 server which is in a chroot. In my opinion, we should probably not release stable stretch with bind9 in this state. This is what I get in systemctl status: ene 19 13:38:04 named[1020]: ENGINE_by_id failed (crypto failure) ene 19 13:38:04 named[1020]: error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: ene 19 13:38:04 named[1020]: error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:467: ene 19 13:38:04 named[1020]: error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:390:id=gost ene 19 13:38:04 named[1020]: initializing DST: crypto failure ene 19 13:38:04 named[1020]: exiting (due to fatal error) ene 19 13:38:04 systemd[1]: bind9.service: Main process exited, code=exited, status=1/FAILURE Please, apply patch by Marc Haber. If you don't have time of whatever, please ping us to perform a NMU or something. Best regards.
