richadams

6 ms·

1.
by richadams 8y ago
There are some good additional resources referenced in the docs here: https://response.pagerduty.com/resources/reading/ Specifically, Google's SRE books are particularly useful ( https://landing.goo
2.
PagerDuty Security Training(sudo.pagerduty.com)
3 points by richadams 8y ago|0 comments
3.
by richadams 9y ago
https://spectreattack.com/ Information site with some more information, and links to papers on the two vulnerabilities, called "Meltdown" and "Spectre" (with logos, of course). ( https://meltdo
4.
PagerDuty Incident Response Documentation(response.pagerduty.com)
5 points by richadams 10y ago|0 comments
5.
by richadams 11y ago
A fiber cut in Oregon could be responsible ( https://puck.nether.net/pipermail/outages/2015-June/007906.h... ). I've been seeing connectivity issues with us-west-2 for most of the day. There was also a fib
6.
by richadams 11y ago
They're currently beta testing a new (more modern) site: https://beta.united.com/ual/en/us/
7.
by richadams 11y ago
"Bugs that are eligible for submission: ... The ability to brute-force reservations, MileagePlus numbers, PINs or passwords" "Do not attempt: ... Brute-force attacks" This seems contradictory. I assume the intent is to n
8.
by richadams 13y ago
Someone else pointed this out too. The goal of the tip is really to stop users SSHing in just to fix that one little thing, so you could still allow your automation frameworks SSH access and just disable it for users (the idea is to disable
9.
by richadams 13y ago
Doh, I feel stupid now. I only looked at bandwidth costs, not the request prices. That's what I get for editing my post late at night based on reading, instead of based on personal experience. For low bandwidth, you're absolutely
10.
by richadams 13y ago
Yup, this was the intention. You could still allow your automation processes SSH access, just disable it for your users. The idea is that if a user can't SSH in (at least not without modifying the firewall rules to allow it again), it
11.
by richadams 13y ago
Ah, I wasn't aware of that, very good point! The goal of the tip is really to stop users SSHing in just to fix that one little thing, so you could still allow your automation frameworks SSH access and just disable it for users.
12.
by richadams 13y ago
Perfectly valid. This particular tip certainly seems to have caused some great discussion! It worked for my particular case, but I can definitely see it not working for everyone. I've added a link to this thread to my tip, and expanded
13.
by richadams 13y ago
I'll admit I hadn't really look at this in depth, using S3 without a CDN solved a particular use case I had a while ago, and it just seemed unnecessary to add a CDN in front of it. I've been doing some reading today, and it s
14.
by richadams 13y ago
Just disabling inbound SSH connections, the servers can still SSH out to other systems to pull in files, configurations, clone git repos, etc. It's just a way to stop yourself from cheating and SSHing in just to fix that one thing, ins
15.
by richadams 13y ago
I think the problem is that I've made it seem like a strict rule in the article; "You must disable SSH or everything will go wrong!!!". It's really just about quickly highlighting what needs automating. Like you say, som
16.
by richadams 13y ago
Wow, didn't know about pre-signed URLs, very useful. I've added this info to my article, thanks!
17.
by richadams 13y ago
Thanks, fixed.
18.
by richadams 13y ago
Great point with regards to IAM roles. The applications I've worked on don't download things from user-defined URLs, so this never even occurred to me. Is the purpose of blocking 169.254.169.254 important because it could potentia
19.
by richadams 13y ago
Great post, I had no idea you could do this with ELB. I've added your link to the additional reading list in my post, thanks for sharing!
20.
by richadams 13y ago
Absolutely, great point! AWS isn't for everyone, and there can be lots of cases where it's cheaper to use dedicated hardware. Shop around before jumping in. I've added this as a new tip at the end of the article (crediting yo
21.
by richadams 13y ago
This is correct. The tip about disabling SSH isn't about security, it's just about quickly highlighting areas where you're not automated. When developing an application for example, it's often necessary to SSH in to play
22.
by richadams 13y ago
Thanks for the tip! CSS updated.
23.
by richadams 13y ago
Oops, sorry about that. Should be fixed now.
24.
AWS Tips I Wish I'd Known Before I Started(wblinks.com)
606 points by richadams 13y ago|149 comments
25.
by richadams 13y ago
I encourage anyone who's avoiding taking part because they don't know assembly or reverse engineering to at least give the tutorial a try, you might just surprise yourself! Having not really touched assembly that much before, I fo
26.
by richadams 13y ago
Seems a bit harsh to fire someone for that. People make mistakes. If anything, you know that this person isn't going to make the same mistake ever again. Of course, if they do, then firing might be the way to go. First time mistake, se
27.
by richadams 13y ago
He "reviewed" the other location too. http://www.yelp.com/biz/sauce-san-francisco#hrid:-L6eTQeqhf5...
28.
by richadams 13y ago
Reminds me of BT Tower in London, built in the 60s. Despite being quite a tall and recognisable structure that obviously exists, it was considered an official secret and didn't appear on any maps until the mid-90s.
29.
by richadams 13y ago
Later in the page (in the "Hardening" section), they mention that they've switched the forums to use Ubuntu SSO for authentication, instead of needing to store forum passwords.
30.
How to Protect Yourself Against Insecure Websites(wblinks.com)
1 points by richadams 13y ago|0 comments

More ›