News for hackers. Stuff that matters.
Re:Kubernetes Failure Stories by raesene9 on Wednesday June 12, 2019 @05:16PM (#20169392)
I've seen short-lived certs as a suggested workaround for the lack of revocation and as a user that might be the best option.

That said the distributions I've seen that make use of client certs, don't do that (typical lifetime for a client cert is 1 year), so I'm guessing a load of people using k8s will have these certs floating about...

Re:Kubernetes Failure Stories by zxcmx on Wednesday June 12, 2019 @08:49PM (#20170893)
It’s a mental shift similar to using iam assume role sessions rather than static keys with perms right on em.

Powerful creds should be limited in lifespan and machine issued to users in a transaction that involves mfa.

We built our own but Gravitational Teleport I think has these patterns in a product.

The other issue even if you get certs right is service tokens (an admin could have grabbed a copy of one and they can be used from outside cluster) so want to keep that api wrapped IMHO.

Re:Kubernetes Failure Stories by zxcmx on Wednesday June 12, 2019 @10:54PM (#20171469)
As an aside, if you want revocable, non expiring user creds you would be better served by bearer tokens.
Re:Kubernetes Failure Stories by raesene9 on Thursday June 13, 2019 @02:59PM (#20177661)
True, the only real in-built option in k8s land for that is Service accounts, which aren't designed for user auth. but can be used for that purpose.