Live data from Hacker News

Alpine Linux Docker images have NULL for root password

cve.mitre.org

101–110 of 203 posts

Re: Alpine Linux Docker images have NULL for root password

#101

Earlier quoted context omitted.

I've no idea why you wouldn't use Ubuntu which is only around 40mb, has a sane package manager and a standard glibc.

Ubuntu is 40MB but if you add a few packages with tons of dependencies it can quickly reach 800MB. Alpine has much more reasonable dependency trees.

--no-install-recommends is your friend

Re: Alpine Linux Docker images have NULL for root password

#102

Earlier quoted context omitted.

My inability to personally audit systemd would be at the top of the list.

Why would anyone run an init system inside a container? Just run the process. Let whatever is managing your container restart it if the process quits, be it docker or K8s.

Here is one reason: https://news.ycombinator.com/item?id=10852055 (TL;DR - default signal behaviour is different for PID 1).

[Edit - fix link]

Re: Alpine Linux Docker images have NULL for root password

#103

Earlier quoted context omitted.

My inability to personally audit systemd would be at the top of the list.

Why would anyone run an init system inside a container? Just run the process. Let whatever is managing your container restart it if the process quits, be it docker or K8s.

Because sometimes it is easier to ship one thing to customers than 10 different images and several different run manifests.

There's plenty of other reasons.

Re: Alpine Linux Docker images have NULL for root password

#104
post #22
post #19

Earlier quoted context omitted.

For anyone who want a small image but with glibc, https://github.com/GoogleContainerTools/distroless is a good choice, especially if you are writing in static linked language e.g. Go and Rust.

For Python I'd also highly recommend Clear Linux for raw performance. It's not quite as easy to get started as with something like Ubuntu though.

docker pull clearlinux/python

https://github.com/clearlinux/dockerfiles/tree/master/python

Re: Alpine Linux Docker images have NULL for root password

#105
post #67

Earlier quoted context omitted.

Please don't do this anymore. End-to-end encryption is extremely easy to set up and maintain. P2PE will absolutely lull you into a false sense of security.

Everyone seems to think E2E encryption is needed everywhere (I know because the security guys at work think it is needed everywhere, even for everything inside a VPC), but even AWS here is advertising the fact that you don't need to do this: https://aws.amazon.com/blogs/aws/new-tls-termination-for-net... >Today we are simplifying the process of building secure web applications by giving you the ability to make use of…

but without tls amazon can "decrypt" your traffic and see whats inside. its one thing to have a backdoor inside a server that they rent to you that would have to be actively exploited and another to passively clone the traffic and analyze it in the name of making the service better.

Re: Alpine Linux Docker images have NULL for root password

#106

Earlier quoted context omitted.

Adding a shell seems antithetical to deploying production code as a static-linked binary, not to mention an expansion of the attack surface of the container.

Without a shell, how does one debug if anything goes wrong?

With remote debugging?

Re: Alpine Linux Docker images have NULL for root password

#108
post #98

Earlier quoted context omitted.

Without a shell, how does one debug if anything goes wrong?

Reading logs/traces on your log aggregation service and reproducing in a dev system?

How do you debug in the dev env without a shell?

Re: Alpine Linux Docker images have NULL for root password

#109
post #67

Earlier quoted context omitted.

Please don't do this anymore. End-to-end encryption is extremely easy to set up and maintain. P2PE will absolutely lull you into a false sense of security.

Everyone seems to think E2E encryption is needed everywhere (I know because the security guys at work think it is needed everywhere, even for everything inside a VPC), but even AWS here is advertising the fact that you don't need to do this: https://aws.amazon.com/blogs/aws/new-tls-termination-for-net... >Today we are simplifying the process of building secure web applications by giving you the ability to make use of…

If you trust Amazon to know your risk profile better than your security people, you have a management problem of some sort.

Re: Alpine Linux Docker images have NULL for root password

#110
post #67

Earlier quoted context omitted.

Unless you're behind a load balancer which terminates TLS and the traffic you deal with is purely http.

Please don't do this anymore. End-to-end encryption is extremely easy to set up and maintain. P2PE will absolutely lull you into a false sense of security.

It does not matter how easy it is, what is the security threat you are mitigating with E2E encryption? In a large scale system it is often not trivial to build a proper E2E, far from being impossible though.
Post reply on HN