![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
It’s a great tool for interface design and visualization.
It’s a great tool for interface design and visualization.
I had a colleague at work years ago who did his Master’s thesis on network scanning. He ran a PoC in the company’s network and had all the printers print hundreds of pages.
We learned that printers suck and that we should always know our payloads and targets 😁
Check out openvas.
https://github.com/greenbone/openvas-scanner
I use Nessus professionally, they are somewhat similar. I can’t decide which one has the worse user interface.
I’m a big fan of hashcat for this use case myself! I route it through WS, however. I like being on the bleeding edge.
The firewalls are all backdoored too!
Caring about the technology of an app more than about its privacy is really strange to me, but you do you.
You can collaborate on WhatsApp or Signal as well, both messengers are using the end-to-end encrypted Signal protocol. Even in group chats. Telegram is not E2EE per default.
Of course, with WhatsApp Meta collects all your metadata so they have a very detailed network of basically all the people in this world… At least without all their messages.
Messages are only end-to-end encrypted if you use the Secure Messaging option. Otherwise everything passes the server in cleartext.
That means that anyone with access to those servers can read your messages.
Telegram is a security disaster.
Not Ruby sure what you’re saying, but I dream of getting strangled by a Python that can’t C#. 🤤
They are not just middlemen, they control the entire sales platform - both buyer and seller.
“Always” is a really strong word that you should not be using in this context since it’s just not true.
Who is Ian?
… could.
Or he (and anyone else) could go and do one of 20000 other potentially way more interesting things with their life.
Imagine that?
IPv6 is not made with internal networks in mind lol
I’m not sure I follow you - if someone can compromise the key material on my phone that is protected by a different factor, then it doesn’t matter whether the 2FA is server-side or not, it’s compromised either way.
Marketing™️ I guess? :P
But probably because YOU don’t have to fuck around with servers, for you it’s just an upload of a function.
You need to check out public key cryptography and digital signatures. Those are the basics of Fido.
When the private key is bound to a device it is not possible to fake or steal it through conventional methods. Passwords are the weakest link and an easy target for attackers - passkeys basically solve that.
User adoption depends on implementation, but everything is easier than remembering a secure password or using a password manager for most people. There needs to be an easy and secure way to distribute passkeys across devices, and any backup mechanisms may be a weak point. In any case: still better than passwords.