Comment Re:Will x86 ever be royalty free? (Score 1) 34
x64 is the important one at this point.
x64 is the important one at this point.
Laptops remain the domain of intel.
Also you don't need to upgrade CPU for many years now.
Athlon was great in P3-P4 era. Bulldozer sucked monkey balls and got utterly crushed by intel's offerings at the time. It wasn't until ryzens that AMD recovered.
In our case, it wasn't "frowned upon". It was so harshly enforced that we had the dumbest fucking event during my early tenure when a bunch of high flying retardmins decided to enforce the "no warez" policy by taking down the local student network's DC hub and getting students who used it temporary university expulsions. They succeeded too for several key figures who administered said hub.
This was a massive bout of idiocy, resulting in easily predictable situation where student network was basically unusable from 17 to 2 after they managed to take the DC hub down. Basically everyone came home from uni, and instead of grabbing their porn, warez, gamez, etc from others on the intranet, they vacuumed them from outside DC hubs, emule, etc. It completely overloaded the edge node, which was never supposed to carry that amount of traffic. I actually ended up getting ADSL for personal usage for a while, because university internet side was just utterly fucking useless at those times for months.
This had to do with a mix of having a couple of high flying admins who were adamant that copyright infringement is the worst crime ever, and national university network itself did in fact have pretty gnarly rules in this regard. To the point where just receiving those standard blackmail letters saying "we found this and this address sharing this file on this service" had those high level admins contact us front line admins and demand we disconnect the port of the person involved on the building switch. I.e. total loss of internet connectivity with no warning and minimal evidence.
Commercial ISPs don't do this sort of stupid shit, because frankly it isn't in their interest to screw over their paying customers. But on university network, students aren't technically paying customers. Student housing association is. And they didn't really care.
The weird part is that we seem to be in agreement, as I outlined early on. I completely agree that having IPv6 available to those who know what they're doing is a good thing.
I do what I preach here. My home connection uses ISP that has full IPv6 support. In many ways, it actually sucks at consumer level still, because everything from software firewalls to many apps on phones are just obviously not ready. So many IPv6 related bugs. Good lord, so many IPv6 related bugs...
And that's for someone who used to do this sort of config for a living.
You put fully discoverable not behind NAT IPv6 in hands of average people? Their fridge will be sending spam mail to boomers in US within a month or two. It's really, really not good.
You would need to heavily re-frame the context to claim difference to be even a little bit relevant.
Forgot the finisher. Guess how good OS level security is on consumer grade IoT?
They're the current XP.
Thanks for sharing. I'll be glad to tell all the people that got wormed back in 2000s after exposing their IP over Emule, DC, etc peer to peer connections that got scanned on connection to see if there's a vulnerability didn't happen. All the ads popping on their machines were imaginary, and they were totally not being used as spam boxes, slowing their machines to a crawl. Heck, the emails we had to send these people to clean their computers were probably sexual harassment or something actually. #meetoo didn't make it in time I guess.
Incidentally, do you also teach your father how to fuck?
The funniest part here is that this sounds like you googled CURRENT popular attack vectors, and assume that is what was happening in 2000s. You sound utterly unaware that current vectors exist because the primary vector of 2000s, that of extremely weak OS level security on XP, have been mainly mitigated from Vista onwards.
Also script kiddies became paid actors, so both "who does it" and "how it's done" changed dramatically.
In most cases, such reports come not with just ip, but ip and port used for the specific reason you mention, yes.
I know some of the people who started HMD. They literally leased space almost opposite of Nokia headquarters building in Keilaniemi in Espoo when they started. You can find the address printed on the old phones (Karaportti 2 Espoo), and if you look at it in google maps, you'll see that it sits right next to Nokia corporate campus.
They had zero factories. The company just licensed the rights to the brand from Nokia, and then went shopping for OEM to make their phone designs in China, and settled on FIH Mobile. This is why early HMD phones were "designed in Karaportti 2 Espoo Finland, made in China/India" for a while.
To my knowledge they have indeed shifted from Nokia branding lately, and you could argue that since FIH Mobile is a subsidiary of Foxconn, they are sorta kinda owned by Foxconn but not really.
When you're on a university network, you sign away a lot of privacy because university networks are generally for studying and research, not general use.
I.e. no porn, no warez, etc was among the rules, and it was in fact enforced. At least on our network.
They already do all those things. It's called "business internet" etc.
It's way more expensive than residential at same speeds, in large part because you need to pay for significantly higher support overhead.
As for owning your customer routers as an ISP (figuratively as in you configure and get telemetry from them remotely), that's already pretty common. In large part because data mining customers' devices and usage patterns is valuable at scale. A lot of ISPs across the world already just sell you a "recommended" router for their specific connection, which will often require to be remotely activated on that specific ISP's network to even begin working.
This is actually a very good reason why you should insist on bringing your own router to hook up your LAN to WAN, rather than using your ISP's offering. As long as you know how to actually configure such a router yourself, which nowadays is mostly automatic anyway.
Not a faintest clue. I just remember having to do a lot of relevant maintenance work with remapping things and documenting them for the new system, which is what always falls in the lap of frontline admins when high flying upper level admins make decisions on "how things should be" and it will of course be taken care of by frontliners.
I can't even remember apartment numbers any more from that time though. Too long ago.
Worth noting that HMD is basically "old Nokia Mobile Phones guys that started a company on location on the opposite side of the street of the old headquarters".
Haven't been doing well though. I know a few people who worked there, and they seem to have mostly refocused on third word markets last I checked.
Most people don't seem to realize that this is a completely different Nokia. Nokia Mobile Phones was an entirely different unit of the parent company that hasn't been a part of current Nokia in a long time (they sold it in 2014 to Microsoft).
This is talking about Nokia Networks (former Nokia Siemens Networks). It's an IT infrastructure company.
Put your Nose to the Grindstone! -- Amalgamated Plastic Surgeons and Toolmakers, Ltd.