For other JS developers the stuff about await isn't relevant. It's not the same as a JS async/await
In JS an await is just syntactic sugar around a then() on a promise. The Await in the article is a method to block the thread until a promise resolves, there is no equivalent in JS.
.NET has a similar mechanism with Task.Result with similar pitfalls
I've recently been doing some hobby coding on a Commodore 128 and I'm getting the hang of editing basic programs without being able to edit inline very well.
I use the list command to dump out sections of the program until I find where I want to edit and then add / edit lines whilst I can still see the listing at the top of the screen.
> You just need to increase the size of the funnel. If you were going to interview 100 people, interview 150.
Then you are not in the "lowering the standards" part but in the "discriminating against men" part.
You cannot turn a 70/30 gender ratio into a 50/50 gender ratio without looking at the gender (Edit: When considering that all are all above the hiring bar).
My sentence did not end at the point. You cannot change the ratio without specifically looking at the gender, that is, specifically hire more of one group (because of their gender) and less of the other group (because of their gender).
Put another way if you spend 20k hiring and you get a 9/10 male developer you could spend $30k increase the size of the funnel and get a diverse hire of the same quality.
Most charitable explanation is that OP is just adding some color to their characterizations. Least charitable explanation is that subconciously or not OP perceives young "females" in positions of authority as being unfit for their positions and likes to add plausibly deniable fuel to that flame.
Perhaps an unpopular opinion around here but I see nothing but positives in this announcement.
This move towards a "good" Microsoft has been going on for a decade, ASP.NET MVC was released as Open Source in 2009. Seeing where they're going with .NET core, VSCode and TypeScript makes me pretty confident they will be good stewards of the site.
Microsoft had their own open source hosting solution Codeplex but closed it and migrated all their stuff to GitHub so they could be where the community was. That was a bold move and I think demonstrates how they see the community now. This isn't the Microsoft of the 90's.
GitHub is great but it's not profitable and I'm sure there are lots of improvements they could make with a bit of a cash injection.
On the flip side if Microsoft stuff it up or there is an exodus from Microsoft because people hate Microsoft, that's not such a bad thing either.
There are great alternatives out there, it's not the same landscape as when GitHub launched, everyone's learnt from GitHub, GitHub's biggest feature is the network effect. Everyone has an account and it's super low friction to contribute there. If we can break that a bit and everyone has an account at 2 or 3 places I think we might see some great innovation as competitors try to differentiate themselves.
Follow up, that same RELEASE mode .NET hello world app shows 153MB in the VMMAP tool used in the blog post, so i's not entirely because of the configuration.
I think the issue is that the tool is showing you what is mapped into the address space of the process which may not use any memory. It could be mapped files or copy on write pages etc.
When I started that post I used the DEBUG build because I (mistakenly) thought that was the only was to get the pdb symbols, but I was wrong about that.
I think that I'll update the post with RELEASE mode screenshots, because having DEBUG ones just confuses things. Very few people (no-one?) will be running a DEBUG version of the CLR in real-world situations, so it's a bit confusing to use it.
My first thought was relief, thank god I'm not using Cloudflare.
Where would you even start to address this? Everything you've been serving is potentially compromised, API keys, sessions, personal information, user passwords, the works.
You've got no idea what has been leaked. Should you reset all your user passwords, cycle all or your keys, notify all your customers that there data may have been stolen?
My second thought after relief was the realization that even as a consumer I'm affected by this, my password manager has > 100 entries what percentage of them are using CloudFlare? Should I change all my passwords?
What an epic mess. This is the problem with centralization, the system is broken.
I find it really interesting that they registered that particular misspelling and they both point to the same servers. I can see doing this for some obvious domains like gogle.com, but the distinction there is simply that r+n looks like m.
Probably a really obvious answer here, but my guess is that they are trying to help people throw off the scent of someone browsing a history.
I think it's more likely that they bought the domain to prevent scammers from trying to bait users onto a fake site and enter login info, and since they have it why not redirect traffic.
Not everyone uses Cloudflare for their proxying service. I use them purely for my DNS, but don't have the MITM proxy enabled at all. His scraping is a better idea probably.
> My second thought after relief was the realization that even as a consumer I'm affected by this, my password manager has > 100 entries what percentage of them are using CloudFlare? Should I change all my passwords?
Yes. Right now. Don't wait for the vendor to notify you.
> What an epic mess. This is the problem with centralization, the system is broken.
My password manager has > 500 entries. Changing all the passwords....isn't going to happen any time soon.
If it only took 60 seconds per site, it would still take eight hours to change them all.
Might change a few key passwords, though. Couldn't hurt. I only have a couple of bank/financial passwords at this point. And my various hosting service access passwords.
Anything else is not worth the hassle -- and mostly would have 2FA anyway.
Your argument essentially revolves around "what are the chances I'll be compromised!?" rather than focusing on "What's the potentially affect of getting compromised" Most people with data or access rights which have several orders of magnitude of value relative to 8 hours worth of labor.
The decision to wear a seatbelt isn't driven by the probability of needing it, the decision is drive by the magnitude of exposure to an event where you would need it.
> Your argument essentially revolves around "what are the chances I'll be compromised!?" ...
You misunderstand. My argument is explicitly around "What is the potential effect?" That's why I listed changing financial passwords is on my list of things that I might do. (Though see below for why I won't.)
If I only change passwords where someone can do real damage (my primary social media accounts, my accounts that have a current, saved credit card, and any hosting-related accounts) then I've already hit the 98th percentile in damage avoidance. And as I pointed out above, most (all?) of those accounts are unaffected because they don't use CloudFlare at all.
If someone has stolen my password to the Woodworking Forums, and they ... what, post rabid alt-right spam in my name and get me banned? Oh well, either tell them that it was hacked, or if they don't believe me, let that account die and create a new one, if I ever decide to go back and post something again. No big deal. I haven't used it in years anyway, and I can create unlimited new (wildcard-based) email addresses on any of several domains I own.
Aside from the top 10-15 sites I use, I rarely have logins that are that important, anyway. So I'm totally basing this on worst-case damage assessment, not on "how likely it is I'm attacked."
AND...I just looked through all of the top sites I use, and according to the HTTP header, none of them is served using CloudFlare at all (I only checked the index page of each, but none have the telltale CF-Cache-Status headers). No financial sites, no shopping sites that have my credit card, no social media sites. So where's the fire exactly?
> In the case of seat belts that's probably because the cost of your life is infinity.
The cost of your life is much higher than your blogger account, but it's not literally infinite, even from your own perspective.
If it were truly infinite, then it would be irrational for you ever to take any action that were not 100% motivated by the desire to protect your life. (Not just "never take any risks", but literally irrational not to actively spend every waking second solely on that goal).
I have been reluctant to use a service that keeps my passwords for me in the cloud.
Instead I'm using KeePass. KeePass is open source and has its "full stack" of encryption available for review. For LastPass I need to trust they're doing everything right, and that a government actor hasn't asked for some kind of backdoor. It's so easy to screw up security that I'm more comfortable trusting two levels of security: That KeePass has its encryption done right, and that Google Drive keeps my KeePass file out of the hands of bad-guys.
LastPass would become a single point of failure compared to what I'm doing: They just need to make one mistake and suddenly any bad guy gets all of my passwords.
LastPass uses local encryption to enable LastPass to have Zero knowledge of users passwords. This means that user's passwords aren't passed in the clear even inside a TSL session.
So LastPass isn't the password manager mentioned in the post.
No, the ones I consider to be "important" have 2FA.
When I log into the Woodworking Forums, I have to use a password. If someone steals my Woodworking Forums authentication and posts as me there, um....Oh well. Sucks, and I'll clean up the mess.
Glancing through my password vault (kept in KeePass, for those wondering) I have some in there that I literally haven't used since before Cloudfare was founded, like the Creative Labs developer site.
There is no reliable way to check. The problem is that even if you verify that a site isn't using CloudFlare now, that doesn't mean that they didn't use it in the past (and you'd still be affected).
In other words: Just assume that everything has been compromised. With how much of the web CloudFlare controls nowadays, you're not going to be far off anyway.
Weird. I read the Cloudflare blog entry (<https://blog.cloudflare.com/incident-report-on-memory-leak-c...) at the bottom of the linked Chromium bug tracker page and they make it sound like it's fixed (the implication being that now would be the time to change all my passwords…)
The problem is fixed in that as far as we know no new data is being made public.
...but since this bug has been out in the wild since perhaps 2016-09-22, now is indeed, the time to go and reset your active sessions and change all your passwords.
If your site is served through Cloudflare, assume it's all out there because it might be. Standard Big Red Button(tm) procedure.
I don't run any particularly impressive sites but I'll be resetting passwords today. Also cycling things I use behind Cloudflare like DigitalOcean passwords/API keys.
It's supposed to be read-only Friday, Cloudflare :(
I won't take the initiative of changing passwords, and I will only be doing it for services that ask me to do it.
In my opinion, if my accounts get compromised because the provider uses Cloudflare and leaks my data all over, it's their fault, not mine... It's not my job to guess which services are using Cloudflare, which ones were affected... and further, if my account gets compromised, others presumably will.
(PS: Of course you may need to change passwords if you reuse passwords from one service to the other, but obviously you shouldn't be doing that in the first place.)
If someone runs a red light, broadsides you while you're in the intersection, and leaves you paralyzed... it is their fault both morally and legally... but it still sucks to be you since you bear the consequences regardless of fault.
While this event is orders of magnitude less severe than my example, depending on the service that could be compromised there can be sufficient repercussions that you could not be made whole or avoid on-going inconvenience through the legal system or other acts of the genuinely responsible party.
I absolutely get and sympathize with where you're coming from... but you may want to check a few of your more important accounts none-the-less :-)
