Bug#987353: CVE-2020-8903 CVE-2020-8907 CVE-2020-8933

2021-05-16 Thread Theodore Y. Ts'o
On Thu, May 13, 2021 at 09:56:53PM +0100, Marcin Kulisz wrote: > > I hope that we're be able to change it, but for me fundamental > question is if Google is interested in participating in effort to > keep those packages in Debian main and if so what resources can be > committed to do so. From my

Re: What belongs in the Debian cloud kernel?

2020-04-03 Thread Theodore Y. Ts'o
On Fri, Apr 03, 2020 at 10:05:03AM +0200, Bastian Blank wrote: > On Fri, Apr 03, 2020 at 09:32:01AM +0200, Emmanuel Kasper wrote: > > IIRC Digital Ocean and AWS have it, but for instance Vultr does not. > > - DO > - AWS > - Azure > - Google on request > >

Re: lack of boot-time entropy on arm64 ec2 instances

2020-01-09 Thread Theodore Y. Ts'o
On Thu, Jan 09, 2020 at 07:15:20PM +, Jeremy Stanley wrote: > On 2020-01-09 13:18:24 +0100 (+0100), Adam Dobrawy wrote: > [...] > > I wonder if the correct criterion for the cloud image is > > compatibility with AWS and GCP only. I suppose a large number of > > deployment are based on private

Re: lack of boot-time entropy on arm64 ec2 instances

2020-01-08 Thread Theodore Y. Ts'o
On Thu, Jan 09, 2020 at 01:11:41AM +, Luca Filipozzi wrote: > > (It's not like RNG quaility is a new problem... why didn't > virtualization approaches include host-to-guest RNG passthrough from the > beginning?) Virtio-rng has been around since 2008 (over a decade), and it provides

Re: lack of boot-time entropy on arm64 ec2 instances

2020-01-08 Thread Theodore Y. Ts'o
On Wed, Jan 08, 2020 at 02:48:13PM -0500, Noah Meyerhans wrote: > The buster arm64 images on Amazon EC2 appear to have insufficient > entropy at boot, and thus take several minutes to complete the boot > process. > > There are a couple of potential fixes (or at least workarounds) for this >

Re: Oracle Cloud Infrastructure

2019-01-01 Thread Theodore Y. Ts'o
(The statements and opinions in this e-mail are mine, not Google's.) On Tue, Jan 01, 2019 at 07:24:19AM +0100, Thomas Goirand wrote: > > Why didn't we use cloud-init? For pretty much the same reason the other > > cloud vendors haven't, and there was fair bit of discussion about it at > > the

Re: Oracle Cloud Infrastructure

2018-12-31 Thread Theodore Y. Ts'o
On Mon, Dec 31, 2018 at 10:56:51AM -0500, Paul Graydon wrote: > Why didn't we use cloud-init?  For pretty much the same reason the other > cloud vendors haven't, and there was fair bit of discussion about it at the > cloud-init summit back in August. RedHat doesn't backport features.  The > Redhat

Re: Oracle Cloud Infrastructure

2018-12-30 Thread Theodore Y. Ts'o
On Sat, Dec 29, 2018 at 08:41:01PM +, Jeremy Stanley wrote: > To echo the sentiment, I too am not that keen on images which need > provider-specific daemons installed to make them viable. As a > sysadmin for applications which span multiple providers, it's more > useful for me to be able to

Re: Allowing login via (serial) console by default

2018-12-19 Thread Theodore Y. Ts'o
On Wed, Dec 19, 2018 at 02:21:33PM +0100, Bastian Blank wrote: > On Wed, Dec 19, 2018 at 01:58:26PM +0100, Vincent Caron wrote: > > I've been using permanent login-less consoles in my LXC containers, > > because it's very convenient. They actually launch 'getty -l bash ttyXX' > > which bypasses

Re: Who updates the debian-cloud-testing images in GCE?

2018-11-26 Thread Theodore Y. Ts'o
On Mon, Nov 26, 2018 at 10:23:40AM -0800, Zach Marano wrote: > Hi Ted, > Actually it is the Google Cloud team right now that owns that project and > and it is best effort to publish anything that works there. Eventually, the > Debian Cloud team will take ownership of producing testing images using

Who updates the debian-cloud-testing images in GCE?

2018-11-22 Thread Theodore Y. Ts'o
I noticed recently that the images debian-cloud-testing images were lasted updated in August, which seems quite out-of-date compared to the images in debian-cloud. % gcloud compute images list --project debian-cloud-testing --no-standard-images NAMEPROJECT