Earlier quoted context omitted.
At least the location isn't embarrassing.[1] [1] https://goo.gl/maps/FjQVttcZCpH2
Oh my gosh, that's the Ivey Business School, where I graduated from last year. I didn't expect this to hit so close to home...
Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
781–790 of 1001 posts
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#782Earlier quoted context omitted.
No, the language is bad if using it wrong can leak sensitive data. The choice of language is wrong if you pick such a language in a situation where mistakes can lead to safety or security problems. The first requirement is security.
You can leak sensitive data with any language. C is not used for web development on the client side, yet people abuse security holes in web apps all the time.
What I'm saying is there is no excuse not to take that protection.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#783What is the optimal balance between centralization and decentralization? Most people in this thread are complaining about how using a big centralized service (cloudfare) causes so much damage when security issues come up, and yet I have seen many people advocate using a single password manager (like 1password) to which this exact type of huge security problem can happen (your password manager is the single point of s…
Also there's the 2-factor stuff to protect you when you somehow lose your manager's master password. What protects you when the proxy in front of you misbehaves and exposes your shit?
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#784Earlier quoted context omitted.
I am confused - why is 1Password is using anything but iCloud or Dropbox? Those are the only options I see (and "Folder" which is presumably just local).
They have "for Teams/Families" options now that appear to use a proprietary, server-side sync, instead of the safer guarantees of the traditional client.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#785Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#786Earlier quoted context omitted.
No, the language is bad if using it wrong can leak sensitive data. The choice of language is wrong if you pick such a language in a situation where mistakes can lead to safety or security problems. The first requirement is security.
But - I can't think of a single language in which using it "wrong" might not lead to info leaks? Any language with a runtime has to manage memory somehow at the runtime layer and so similar leaks can occur there depending upon design and implementation, and the wider OS context. At the whole program/application level, when you create your own data structures, you can find lots of ways to leak them to the world.
Using a runtime with a safe language on top is a perfectly good example of doing that.
Logic errors causing leaks will always be a threat, but we shouldn't be leaking because of pointer arithmetic problems in custom C code. Not 2017.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#787Let's be honest. There are holes. More than we care to admit. The truth, if embrassed, could undermine the world's economy. It's just question of when.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#788Earlier quoted context omitted.
So is any CDN.
Forgot about that, thanks. However we can use "integrity" attribute
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#789Earlier quoted context omitted.
Not NSA, but the CIA funds and operates In-Q-Tel[1]. They've funded companies like Palantir and Keyhole (which became Google Earth). [1] https://www.crunchbase.com/organization/in-q-tel
I should have done my research, but I walked away from an accepted offer at a company once I found out they took money from In-Q-Tel.
Re: Cloudflare Reverse Proxies Are Dumping Uninitialized Memory
#790Earlier quoted context omitted.
Without disagreeing, can you give me an example. And it's just a speculation. Shrug.
One simple explanation could be the road was between very large concrete buildings or the area has some sort of GPS interference (there is one place in Tokyo that jumps my GPS and probably others' by about 300m to the same location every time). Another simple explanation is the software has a bug on when it thinks you arrive in some extremely bizarre scenario (hence you both had it happen simultaneously). I don't kno…