• 0 Posts
  • 66 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle







  • Kind of, it’s kind of like using a calculator instead of doing arithmetic by hand when doing load and strain calculations. It’s a tool which cuts down on the tedious (and error prone) parts of engineering but doesn’t replace the expertise. I use it frequently to write code snippets for things I don’t know the exact sytax for but could easily look up. It just saves time.

    Like, we have a guy whose entire job is to understand the ins and outs of a particular bit of modeling software. In the future that will likely be a person who runs the AI which understands the ins and outs of the modeling software. And eventually the AI will replace that software entirely.





  • I am skeptical of this being viable on public Wi-Fi tbh. You’d need to know ahead of time which VPN servers the target will attempt to contact, some information about the target ahead of time, and you need to DHCP poison the entire network prior to the target connecting. That would effectively bring down the network for all but two hosts - the attacker and target.

    I mean at that point, you can also just repeatedly deauth the target until it connects to your spoofed network and do whatever you want, and it would be way less obvious to an outside observer.


  • I’m a bit confused how this is considered a new vulnerability. The IETF RFC which proposes option 121 literally states that malicious DHCP servers could be used to redirect traffic to malicious hosts, and I’m fairly confident that we learned about this exact thing in CCNA school in like 2003 (with regards to router configuration security).

    I suppose the application to a VPN attack might be relatively novel?