workstation

How Many Jeffs Does It Take To Run A Podcast? Jeff Geerling Joins

How Many Jeffs Does It Take To Run A Podcast? Jeff Geerling Joins – Talking Heads Ep.333

#Jeffs #Run #Podcast #Jeff #Geerling #Joins

“Craft Computing”

Welcome to Talking Heads, your once weekly show about everything happening in the world of tech, computers, gaming, craft beer and cocktails.

You too can be a Bad Mother Flipper… Grab our new Minimalist Wallet from

Check out this episode in Podcast form over at…

source

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

19 Comments

  1. if you leave the stream VOD monetized it will tank the recommendations because it's a big video that will get less view time than your average videos and this will confuse the Holy Algorithm. That's why everybody else either puts them private, demonetizes or moves them to a dedicated channel with only their VODs

  2. The "attack" against VPN tunnels is more a feature of DHCP and more a problem in terms of routing / DHCP on the device in general. And it is not new, it was mentioned before.

    However, Jeff seems to have a problem with Jeff. Or am I confusing stuff?

  3. Funny how i am in the phase of putting absolutely everything in the same efficient box. I have a proxmox router+nas+pihole+frigate+jellyfin+haOS 12800h 32gb box that idles at 35w, and I am very proud of it

  4. Its not Fero doctor. Its Freo Doctor and its in reference to the breeze that comes off the indian ocean at Fremantle in Western Australia. Which is kinda funny that its made where you are from as its not a common thing to know outside of Western Australia. Should also mention Freo is the slang term for Fremantle as Aussies tend to shorten words down to something ending in o LOL

  5. Steve Gibson (of Spin Rite fame) has a podcast where he explains exactly how the VPN MITM was done by using a feature of DHCP and why it's technically not a hack because it's using a legitimate feature of DHCP. It's not even exactly an 'exploit'. I'm going to try to paraphrase what he said… Basically, it relies upon an attacker providing a very fast DHCP server that can respond to DHCP requests faster than the normal DHCP server on the network. By definition, DHCP clients don't know anything about the network they are connecting to, so they broadcast a request for connection settings, and they accept fastest DHCP server response as authoritative. The DHCP protocol is doing exactly what it should be doing so it's not really a bug. He also said there may be a way for a client to detect if this is happening to it by sending a special loopback ping and watching to see if the ping comes back on an unencrypted port. He also indicated that option 121 exists because it solves some rather critical enterprise problems, so it can't just be disabled on all clients.

Leave a Reply