Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
l9i
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
l9i
2y ago
Damien Miller
2.
▲
by
l9i
3y ago
> And I think Google has a backup IRC server on AWS, but that might just apocryphal. They (>1) do exist but not on AWS or any other major cloud provider. (Or at least that was the case two years ago when I still worked there.)
3.
▲
by
l9i
3y ago
If you enjoy Organic Maps, please consider supporting them financially: https://organicmaps.app/donate/ . Supporting their serving infrastructure for numerous users is surely costly.
4.
▲
by
l9i
5y ago
Most outdoors activities are safer and more pleasant when there is some sunlight (think: walking through a forest, hiking, swimming in a lake, sports, having a picnic, etc).
5.
▲
by
l9i
5y ago
Interesting that you are asking for the dirt given that DiRT stands for Disaster and Recovery Testing, at least at Google. Every year there is a DiRT week where hundreds of tests are run. That obviously requires a ton of planning that start
6.
▲
by
l9i
5y ago
A Gmail outage would be barely an inconvenience as Gmail plays a minor role in Google's disaster response. Disclaimer: Ex-Googler who used to work on disaster reponse. Opinions are my own.
7.
▲
by
l9i
5y ago
I found a comment that was factually incorrect and I felt competent to comment on that. Regrettably, I wrote just one sentence and clicked reply without providing any credentials to back up my claim. Not that I try to hide my identity, as
8.
▲
by
l9i
5y ago
I unfortunately cannot edit the parent comment anymore but several people pointed out that I didn't back up my claim or provided any credentials so here they are: Google has multiple independent procedures for coordination during disas
9.
▲
by
l9i
5y ago
The safe in question contained a smartcard required to boot an HSM. The safe combination was stored in a secret manager that depended on that HSM. The engineer attempted to restart the service, but did not know that a restart required a ha
10.
▲
by
l9i
5y ago
That's not quite how it happened. ;) <shameless plug> We used this story as the opening of "Building Secure and Reliable Systems" (chapter 1). You can check it out for free at https://sre.google/static&#
11.
▲
by
l9i
5y ago
I can assure you that Google has a procedure in place for that.
12.
▲
Host Identity Based Authorization for SSH
(opensource.googleblog.com)
6 points
by
l9i
5y ago
|
0 comments
13.
▲
by
l9i
5y ago
If you find Andreas' work inspiring and/or useful, you may consider supporting him in pursuing his passion: - https://github.com/sponsors/awesomekling/ - https://www.patreon.com/serenityo
14.
▲
by
l9i
6y ago
Thank you for letting us know Lucian! I shared your comment with our publisher (O'Reilly). (disclaimer: I worked on the book)
15.
▲
by
l9i
6y ago
Confirmed. I was hoping for the platypus but it turns out it was already taken anyway. You can check out the whole O'Reilly menagerie at https://www.oreilly.com/animals.csp . (disclaimer: I worked on the book)
16.
▲
by
l9i
6y ago
In a somewhat snarky reply, I can assure you that the book release was planned long in advance, unlike the outages. ;) (disclaimer: I worked on the book)
17.
▲
by
l9i
6y ago
This book should be suitable for software engineers without security background. There are some sections that might require some knowledge but they are explicitly marked as Deep Dive . (disclaimer: I worked on the book)
18.
▲
by
l9i
6y ago
Le*v*andowski != Le*w*andowski Seriously though, there is no relation that I am aware of. It's a very common surname in Poland (source: https://en.wikipedia.org/wiki/Lewandowski ). (I'm Piotr Lewandows
19.
▲
by
l9i
6y ago
Most of the design principles covered by the first part of the book are quite generic and can be applied to a broad range of systems. If you are working on embedded systems, the Design for Recovery chapter might be a good start since it c
20.
▲
by
l9i
6y ago
Thanks for pointing this out, we're on it (other formats have a similar problem). (disclaimer: I work at Google)
21.
▲
by
l9i
6y ago
We were very much aware that not all companies can afford to staff a dedicated security team. We tried to do our best to make sure that the book is applicable to a wider audience: from startups, to big corporations. (disclaimer: I work at G
22.
▲
by
l9i
6y ago
We did our best to highlight the intersection of security and reliability. I admit there might be more emphasis on security in some chapters, especially those that overlap with the previous two SRE books (that were exclusively about reliabi