sybercecurity

Well, sex and looting, and maybe inventing new music genres.

The legend is that hip hop and sampling started after the blackout in NYC. Some electronic and music stores were looted and the recording equipment eventually ended up in the hands of musicians looking to make a new sound: https://www.rollingstone.com/music/music-features/new-york-c...

Sometimes one large corporation feels like working with multiple smaller vendors. Products are too siloed and don't work together the way they claim, etc.

Don't forget enterprise management. Windows makes it easy to maintain a fleet of endpoints much easier than MacOS or Linux.

Maybe this is in preparation for a LUNIC (lunar RIR). Or better: LUNATIC - Lunar Time and Network Information Center.

In the 70's we started putting Pigs in Space(https://muppet.fandom.com/wiki/Pigs_in_Space), so now we need the rest of the ingredients for pork and kimchi stew.

BIND9 used to also be the basis for a lot of DNS appliances back in the day, so unless you are running your own recursive server, you might still be running bind, just with a GUI front end.

Hardly a new trend. Young people have always put more trust in friends/peers than older people. Part of growing up is realizing not everyone in your age cohort is trustworthy. Just like how older people have always complained about how young people don't take their advice.

Indirectly, yes. Since they don't understand the details, management just "wants it to work". So too many email admins just give up and make their sending policies as permissive as they can to account for whatever new service marketing is using at the time.

Can't get over paywall, but from experience:

NoVa/DC Sluglines are a cool example of self-organizing communities. There is a set of informal rules and etiquette around passengers and drivers. A lot of it comes from the military background of the participants. The locations of pickup/dropoff sites were largely spread word of mouth in the pre-social media days.

I always assumed they were thinking "Well, it's not like there are going to be a lot of ice storms in LA..." and were in a hurry.

True - the purpose was to authenticate, not just encrypt. Years ago, every CA had additional tiers of authentication for certificates that included all sorts of ID checks, corporate records, etc. The idea was that businesses would pay extra for a certificate that guaranteed they were the legitimate brand. However, users couldn't easily differentiate between these levels, so there was no point.

Now people have come to realize a cert basically ties a service to a domain name and that is basically the best you can do in most cases.

Saw a comment elsewhere: It looks more like they are in an ice dancing competition.

This has been posted before - previous thread: https://news.ycombinator.com/item?id=43002242)

The .gov TLD was only for the Federal government in the past, it was opened up later to state/local governments. By then, some had already had <something>.<state>.us, or some other TLD. Most probably thought it was too troublesome to migrate over. That and the fees were more than any other gTLD (though not now).

>...even though it's convenient for travelers

Which is why it will not close. It's easier for Congress members, senior staff, etc. to use rather than the drive out to Dulles of BWI. It's convenient for powerful people.

This has the potential to be very helpful. Donating bone marrow or blood stem cells is uncomfortable* and requires taking time off which makes it difficult for people with job/family constraints. So a pool of potential donors are likely dissuaded from volunteering to donate.

*As a donor (stem cells; the easy one so I'm not a hero), it's not a pleasant experience, but I'm guessing it's way easier than dealing with the actual cancer, so have no grounds to complain.

Public schools around me dropped cursive writing years ago. Old-school Montessori schools (those that follow Assoc. Montessori International - AMI at least) seem to be the only places keeping cursive alive. They teach cursive before print in some cases.

Back then, there was a push to have NoVA be referred to as the "Silicon Dominion". Never caught on thankfully.

Nokia produced several early smartphones. Most ran SymbianOS that showed what was possible. The connectivity wasn't there to make it really useful and this was the age of "smaller is cooler" mobile phones, so they tried to keep the screens small.

I imagine that there were several people in Nokia that understood the potential of a phone that could also act like a mini-computer.

Part of the decision feels like the FCC is looking for whatever leverage they have over telcos and just using that as a vehicle. I'd also like to think that telco companies already due risk assessments (maybe not frequently updated or rigorous as people would like), so how much of an impact would this really be?

(I know...when you "assume" you make an ass of 'u' and me and it also depends on what both sides think "minimum" means).

I've heard these issues referred to as "bug-for-bug compatibility" or "bug-for-bug interoperable". Making sure something works even if it is in violation of a spec since you can't change the other side of the communication.

The most charitable explanation I can think of is that they expect you to use your email account for business, and they may need to pull communication for regulatory purposes? Even that is weird and questionable and usually illegal in that you should not be using personal email for business in a regulated industry.

This link: https://legal-info.lawyers.com/labor-employment-law/privacy-...

says that it might even violate Federal law (Stored Communication Act), though if you give permission it might be more complicated as it could be viewed as "authorized".

Getting strong "LARPing Dawn-of-the-Dead" vibes from some of the footage.

"...this can also be a bad thing, in that the bar to entry in theory is quite low, meaning you might have to deal with people arguing in questionably bad faith, or who don’t have first hand real world experience of the subject."

FWIW, this isn't something that can only happen in the IETF. Lots of other SDOs can have this issue. Some (usually corporate sponsored) participants in SDOs participate solely to slow down/poison work. Usually as an effort to gain market share while things are debated and become the de facto standard rather than allow something they may not implement become standardized.

Yeah I was going to say that "Achilles Heel" makes it sound like it was a previously unknown vulnerability. This is really an intentional access point into the infrastructure that didn't have mitigations in place (or an actual unknown vulnerability) that was used to gain access.

I guess I misinterpreted it - sorry. It must say something that it isn't a big announcement anymore: either it has gotten to the point where people expect it (good operations), or people are expecting DNSSEC to go away (bad for DNSSEC).

Still, with the reliance on the DNS for things, it would be nice to have it be secure. Or a DNS 2.0 that has solves a lot of the current issues with the protocol, but DNS has proven resilient and adaptable enough to continue working since RFC 1023 and 1035.

It was delayed, but was successful. The available metrics at the time showed that many validators did not pick up the new key, or did not store it in stable memory so every time a new VM/container/whatever started up, it had the old key. Once those were fixed, the rollover completed.

That's the problem with doing maintenance on infrastructure used by every host on the Internet. Though efforts to replace DNS with a more distributed model has never succeeded (yet).

Yes, I get the feeling that there were likely other reasons why they wanted the employee gone, but needed a good reason that wouldn't result in a legal complaint.

Even mentioned in a darkly humorous tone in the 1968 movie "Ice Station Zebra" (cold war thriller). The character played by Patrick McGoohan has a line: " The Russians put our camera made by our German scientists and your film made by your German scientists into their satellite made by their German scientists."

>I think it would be more appropriate to tell people to pack an AM radio in the disaster bag we’re all suppose to keep in the trunk.

From dealing with so-called "policy wonks" over the years, having a solution that requires people take action ahead of time and buy something new to replace something they had in the past is a non-starter. They most likely won't listen to anything after that. They are extremely risk-adverse in general so any change is seen as bad unless proven otherwise. It's easier (in their mind) to just force things to stay the way they are since they don't trust people to make decisions.