[Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
Yes, it seems like I just had a stale Chromium process running. Everything is indeed fixed now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
Still hitting this bug on Trusty. chromium-browser 53.0.2785.143-0ubuntu0.14.04.1.1145. Is there any way to temporarily disable CT for _all_ sites via corporate policy? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642955] Re: cryptsetup does not support the 'keyscript' crypttab option when used with systemd
wrong package chosen ** Package changed: upstart (Ubuntu) => cryptsetup (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642955 Title: cryptsetup does not support the 'keyscript' crypttab option when used with systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1642955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642955] [NEW] cryptsetup does not support the 'keyscript' crypttab option when used with systemd
Public bug reported: Our company is using Ubuntu as our main OS now. Before we decided to switch to 16.04 (with systemd) we used keyscript= crypttab option to manage some of our encrypted volumes. Now with Systemd that's no longer possible and we're forced to use upstart, which in itself contains several nasty bugs at this time (these aren't exactly the scope of this bug though). Due to removed functionality that was present in previous release, I still consider this a bug in cryptsetup even though it's related to upstream. I know that systemd introduced a concept of 'password agents' but AFAIK there's no way to automate the process of getting block device keys - because these agents only accept ASCII text (and our keys are already binary, that'd take a huge effort to redo everything to use, say, base64 anyway). ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: cryptsetup keyscript -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642955 Title: cryptsetup does not support the 'keyscript' crypttab option when used with systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1642955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
I have noticed that if the machine has been shut down uncleanly, then the success rate of it getting to boot normally is nearly 100%. Must have to do something with fsck delaying the startup sequence enough for this bug not to trigger? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1364630] Re: init: Error while reading from descriptor: Broken pipe
Happened to me too, and too after upgrade from 15.10 to 16.04. Since we're using crypttab with the keyscript= option, we can't yet use systemd, and it seems like the system affected can boot once in ~5 times fine, suggesting there is indeed a race condition somewhere inside upstart (?) Despite wasting 5 hours of my time yesterday I can't yet gather enough data for a consistent bug report. PS. Considering systemd's inability to coexist with the keyscript= option - maybe we guys should raise a petition so that we can finally be heard? It's a very longstanding issue systemd developers are intentionally turning their heads away from. Don't think that's exactly how open-source software should be built. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364630 Title: init: Error while reading from descriptor: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1364630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
