Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dsl
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
50 ms
·
451.
▲
by
dsl
8y ago
Starting an ISP is relatively easy... get an uplink, some rack space somewhere, a router, hire a smart high school kid for tech support, and you are off to the races. The really hard part is last-mile connectivity. You are either on someone
452.
▲
by
dsl
8y ago
I don't know much about the decapping/chip security process. What is the benefit in selectively erasing part of the chip? How does that help you read the part that isn't erased?
453.
▲
by
dsl
8y ago
Take the OSCP course, it is relatively cheap for the value of the content and it is one of the few certs in security that is respected. From your profile it looks like you work for a big company. Ping some people in security and find out wh
454.
▲
by
dsl
8y ago
For work I am doing, most of the "automated tools" are things I wrote myself and I know what they do. It is up to the engineers working on the engagement to exercise care and avoid causing disruptions to the target or doing things
455.
▲
by
dsl
8y ago
It is up to you to define where your peremiter is, and put your protections there. I generally recommend having the WAF live in front of of apps, but with a small gap that allows your scanners to still access the app. It is important to sti
456.
▲
by
dsl
8y ago
I break into stuff professionally. There is nothing I love more than the "just throw {Cloudflare,Akamai,Fastly,etc} in front of it" crowd. If you are going to deploy a WAF [1] it _needs_ to be at the edge of your datacenter or clo
457.
▲
by
dsl
8y ago
If you get a 404 on the link (like I did), click on Mathematics at the top, then on the article.
458.
▲
by
dsl
8y ago
Have you had a serious sit down conversation with your board? This is exactly why you have a board of directors. If you don't have an external board, start making the rounds to see if you can raise a series and buy him out. (if you see
459.
▲
by
dsl
8y ago
It is obvious Cloudflare has no interest in operating a real recursive DNS service. If they did, they would have provided additional backup IPs for users they knew would be impacted by these issues. Building a production service on what eve
460.
▲
by
dsl
8y ago
http://manpages.ubuntu.com/manpages/trusty/man1/pollinate.1....
461.
▲
by
dsl
8y ago
I said the fix was easy, not that people were actually fixing it. :/
462.
▲
by
dsl
8y ago
I think you are misunderstanding what is going on here. The Signal client on your phone is connecting to a load balancer that Amazon owns. In the initial handshake it lies about what website it is trying to contact, claiming to be looking f
463.
▲
by
dsl
8y ago
Fixing domain fronting is easy. You just match the certificate SANs (or SNI requested domain) to the request Host header. The only problem is it breaks a subset of users who are domain fronting by accident (Think a mobile app that connects
464.
▲
by
dsl
8y ago
But they are. With SNI you are literally lying to the Amazon load balancer, which is one of the two parties of your encrypted communications.
465.
▲
by
dsl
8y ago
Pretty much any NAS you buy today has AFS support. Buy yourself an Asustor or Synology, toss a few drives in, and it will show up automagically as a Time Machines destination.
466.
▲
by
dsl
8y ago
I lost it at the Go business cards...
467.
▲
by
dsl
8y ago
> makes it clear why most programmers should stay away from design. Part of being a good designer is understanding the audience you are designing for. They didn't do that.
468.
▲
by
dsl
8y ago
No, this all started with an email to UX/design of "I want a professionally designed slide deck for this talk I am giving" and they sent it off to an agency. There is no way self respecting Googlers were involved in this shit
469.
▲
New BGP hijack attempted on 6% of all IP space
(radar.qrator.net)
2 points
by
dsl
8y ago
|
0 comments
470.
▲
by
dsl
8y ago
But Amazon really did screw up here. The attackers were able to announce more specific prefixes than Amazon was announcing itself. It was like Amazon said "give me all phone calls for the 415 area code," and the attackers said &qu
471.
▲
by
dsl
8y ago
There is always a server. Your question is do you want to pay someone else to run it for you.
472.
▲
by
dsl
9y ago
Except the space shuttle, international space station, mars missions, hubble telescope, and a dozen other things. But other than that, sure.
473.
▲
by
dsl
9y ago
Same here. Looks like the server broke.
474.
▲
Docker Cloud will no longer scan for security issues without Enterprise account
(success.docker.com)
2 points
by
dsl
9y ago
|
0 comments
475.
▲
by
dsl
9y ago
Verified the vulnerability, but it looks like they have taken down the API now. Hopefully they will publicly acknowledge.
476.
▲
by
dsl
9y ago
I've had to do audits of apps that required you to be connected to a specific Wifi AP (usually with a dev server instance attached) to function.
477.
▲
by
dsl
9y ago
It looks like it is corrected now. I didn't include the year in the original submission, so it must have gotten typo'ed by a mod.
478.
▲
The original pitch for Diablo (1994) [pdf]
(graybeardgames.com)
241 points
by
dsl
9y ago
|
88 comments
479.
▲
by
dsl
9y ago
It's not "serverless," you are just paying someone else to run more of your stack for you. In the late 90s to early 2000s we called this "Application Service Providers" or "Managed Hosting."
480.
▲
by
dsl
9y ago
3. The vulnerability is not real, or you intentionally overstate the impact publicly. Not insider trading, but definitely worthy of SEC inquiry. It's like a short position pump-and-dump.
More ›