Why is it that the folks responsible for deploying physical #security tend to be completely oblivious when it comes to #InfoSec? “We’ve installed all of these cameras and want you to forward these ports from the Internet now.” #HowAboutNo
Remote
Jody Lemoine CD 🇨🇦
@ghostinthenet@hachyderm.io
mastodon 4.7.3Network anarchitect, matrix greasemonkey and packet nerfherder. Freemason, RCAF officer, motorcyclist, CCIE 41436, MikroTik Certified Trainer, MTC*E, Tech Field Day Delegate
481 Followers
484 Following
41 Posts
Joined October 31, 2022
Maybe I’m just a dinosaur. I’m still of the opinion that products and services that help us do things with no requirement for us to understand what we’re doing are ultimately serving us poorly. Yes, #AI can be an example of this, but that’s not alone, nor is it where it all started. Vendors have been pushing products that claim to minimise the need for basic technical skills for years and we’ve bought into it because we would rather invest in technology than our people… or ourselves.
Engaged in a #Windows vs #MacOS vs #Linux discussion the other day that (for once) didn’t devolve into a fan-driven religious war. It got me thinking that the three things that drive our choices are value, consistency, and ecosystem. (I’m sure that there are more. Feel free to weigh in.) In the spirit of RFC 1925 7a (and Meat Loaf) two out of three are usually enough, but we’ll always want it all. Windows and MacOS are pretty good at delivering on two or more, but now I’m wondering if Linux’ lack of adoption on the desktop is related. The value is definitely there, but consistency and ecosystem are sketchier. Thoughts?
One of these days, I'm going to actually internalize the idea that writing #documentation •as• I do something is far more efficient than going back and figuring out what I did when I'm finished.
Perhaps you’re wondering why I’ve called this meeting. #Corgi #CorgiLife #CorgisOfMastodon #DogsOfMastodon #FediCorgs
Something to consider about all of the efforts to sustain #IPv4 so far beyond its original shelf life. #NAT and #IPv6 were thought out at roughly the same time. NAT was a tactical move to stave off IPv4 exhaustion (at the cost of limiting the peer-to-peer nature of the Internet) and IPv6 was the strategic answer for scalable growth. The obsession human beings have to find any excuse to avoid change was highly underestimated. IPv6 took 22 years to become an Internet Standard and NAT became so entrenched that peer-to-peer networking became mostly unnecessary as long as we could continue to laugh at cat memes on our favourite platforms.
This brings us to #platforms. It’s getting harder to host anything ourselves anymore without paying a (usually foreign) IaaS/SaaS platform to do it for us. We now live in an age where data sovereignty and privacy are at the forefront of our thinking and maybe, just maybe, we want other options.
Is our obsession with IPv4 tying us unhealthily to platforms and sacrificing our freedoms?
So… we’ve been using a beeper to train Charles to stop madly barking at the neighbour. He barks, we activate the beeper, he stops. Hoping that he’ll eventually get the idea that he shouldn’t bark at the neighbour, though we may be more hopeful than we should be.
The thing we didn’t consider was #corgi #spite. Ultra-powerful corgi spite. I hit the beeper, he stopped barking, and then promptly turned around to roll in a particularly pungent pile of vermin spoor.
Sigh. Bath time. I should have known something like this would happen.
Replying to
@nixCraft@mastodon.social Preach! (Especially item 3.) Shout that from the mountaintop.
Replying to
@jack_daniel@mastodon.social You can even make a game of it… if you like. 🙂 https://boardgamegeek.com/image/143139/guillotine
Auditor: Can you send a screenshot of the access VPN timeouts so we can demonstrate policy compliance?
Me: (Sends relevant portions of the configuration.)
Them: This is a text file. We need a screenshot.
Me: (Sends screenshot of my terminal session showing the relevant portions of the configuration.)
#InfoSec #NetEng #MaliciousCompliance
Replying to
@beyondmachines1@infosec.exchange Images? Yes. Art? No. Art, by its very definition, cannot be created by a machine.
For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. https://github.com/ghostinthenet/l2vpnLab #MTPC #NetEng
I think I’ve been in this industry for too long. I searched for a synopsis this morning and accidentally typed “synoptics” instead. Last week I was teaching the NATO phonetic alphabet and taught “unicorn” instead of “uniform.” #NetEng #SiliconValley
Replying to
@kasperd @litchralee_v6 @tschaefer @jima It was more a criticism of his pretending that IPv6 doesn't exist than anything else. Still, I would have found his inclusion of an attempt at NAT86 to be highly amusing.
Replying to
@furrfu@mastodon.social That has nothing to do with #NAT. That's just stateful inspection, which existed before NAT was invented. NAT overload (and •only• NAT overload) requires stateful inspection and almost always embeds it, but it’s an independent function from translation. NAT's purpose is to alleviate address exhaustion and nothing more. My home router has a stateful firewall for IPv6 and it provides the same benefits you’re attributing to NAT without doing any translation at all. #NATisNotSecurity
Replying to
@katharta@quietzero.net True… but it’s still friendlier and less complicated than IPv4. We’re just used to the complexities of IPv4 and take them in stride because we do it all the time. (And no, we should •not• be communicating IP addresses verbally… whether IPv4 or IPv6. We should have stopped that nonsense years ago. It’s not like we didn’t have better and more secure options.)
Wow. Fifteen years since I became a founding member of the #FNS. Great experiences, great people, dubious networking. https://flatnetworksociety.com/ #NetEng
We have dozens of relatively simple methods to secure Internet traffic, but we’re often reduced to “just open access through your firewalls from this huge list of source addresses” because too many folks can’t be arsed to do any of those. Keeping it simple is •not• about moving the complexity into the customer’s realm of responsibility. #NetEng #InfoSec
Replying to
Replying to
@hugo Oh, I know... I'm just playing at taking it seriously in order to mock it more effectively. 🙂
Replying to
@tschaefer So we now have to run •three• protocols? 🙂 https://imgs.xkcd.com/comics/standards.png
Replying to
@kasperd @litchralee_v6 @tschaefer @jima This IPv8 pipe dream has no backwards compatibility with #IPv6, so it would •still• require us to run two protocols… or am I missing his NAT86 proposal?
Replying to
@kasperd @tschaefer Agreed. We’ve hit 50% IPv6 deployment (if we use Google as a reference) so we’re in a good position to start using their argument against them. If trying to shore up IPv4 made sense because it was the majority protocol at the time, it’s worth finally committing to IPv6 now that it has taken the crown.
Replying to
@eniko@mastodon.gamedev.place Sir Tim’s vision is still intact. We just need to buy into it again.
Replying to
@michael@backend.newsmast.org It's a good beginning to the discussion. My 2¢? We've been sold an empty bill of goods with respect to the expectation of growth in the social space. If growth is a consideration at all, it's secondary to independence and community engagement.
Replying to
@Cloudslave@aus.social @CarlWatkins@mastodon.social That’s where I am. I still crosspost to both, but the sound of crickets is •much• more pervasive on Bluesky.
Replying to
@mWare@ottawa.place @katharta@quietzero.net Ha! Yes. (Which is fine, as long as it’s •our• DNS. It’s when we hand the responsibility to someone else that it all falls apart.)
Replying to
@ianbetteridge@social.vivaldi.net Whenever this sort of thing comes up, I refer to Beau of The Fifth Column’s video from a few years ago. He said it well. https://youtu.be/0fK_KdcaCN8 #Masculinity
Replying to
@sossalemaire@mamot.fr @HumainVirtuel@mastodon.social @dannotdaniel@hellions.cloud Franglais is a Québécois tradition. 🙂
Hedgehog's tie to Kubernetes potentially allows a cloud-as-abstraction approach to an organization's networks. It's a lot to wrap one's head around, but it has potential. #NFD38
Replying to
@ivan@mastodon.scot @moanos@chaos.social The global ISO standard is month before day. Now, before my US friends start smugly smiling, ISO standard is also year before month.
Replying to
@Daojoan I'm finding that it's not just more traffic, but better engagement too. The experience is a lot like Twitter's... but from 15 years ago.
Replying to
@jerrylevine@mastodon.social Funny, I never realized that that likes on Twitter did anything other than letting people know I liked their posts. In retrospect, I’m glad I wasn’t trying to game the system.
Replying to
@sfoskett …but did they reach out to you on Facebook Messenger? 😉 /me ducks
Replying to
@aeri @0xabad1dea Creative decimal placement can make a big difference too. Move it one place to the left and there’s no need to bring an “8” into play. Sure, we need to redefine the “high” in “high availability” but I’m up for it if everyone else is. #HighAvailability
Replying to
@kasperd@westergaard.social In the spirit of “never attribute to malice that which can be adequately explained by incompetence” I don’t have much to support that… but it’s not beyond consideration either. It •does• fit the “follow the money” test.
Replying to
@paul_ipv6@infosec.exchange @nixCraft@mastodon.social This. This! This!! It’s never more true than when the rebranding happens in the absence of any new product/service development.
Replying to
@tyrant One of those “be careful what you ask for…” items, for sure.
Replying to
@tschaefer I like that it expires in October. Without a valid proof of concept, that’ll be the end of it.
Cloud services, data security risk, and limitation of liability clauses are a bit of a perfect storm. Too many of us use the services because they’re accessible, but we’re often blindly trusting that they will (or can - see CLOUD/NSL considerations) keep our data secure, and don’t consider that we have little to no recourse when they don’t. As always, #security and #sovereignty hold no priority over convenience… until it’s too late. #InfoSec