#qubes — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #qubes, aggregated by home.social.
-
7 #privacy tools experts actually use
https://proton.me/blog/privacy-tools-experts-use
#guide #Android #GrapheneOS #Graphene #Qubes #OrganicMaps #FDroid #RSS #Cape #Tor
-
This Week in Security: Baked-in Malware, Freezers Not Freezing, Zoom Snoops Clipboards, and AI Makes Things Worse, Faster
-
This Week in Security: Baked-in Malware, Freezers Not Freezing, Zoom Snoops Clipboards, and AI Makes Things Worse, Faster
-
This Week in Security: Baked-in Malware, Freezers Not Freezing, Zoom Snoops Clipboards, and AI Makes Things Worse, Faster
-
This Week in Security: Baked-in Malware, Freezers Not Freezing, Zoom Snoops Clipboards, and AI Makes Things Worse, Faster
-
This Week in Security: Baked-in Malware, Freezers Not Freezing, Zoom Snoops Clipboards, and AI Makes Things Worse, Faster
-
SecureDrop Workstation 1.9.0 is now available!
This release hardens the updater against some edge cases discovered during the 1.8.0 release.
https://securedrop.org/news/securedrop-workstation-1_9_0-released/
-
SecureDrop Workstation 1.9.0 is now available!
This release hardens the updater against some edge cases discovered during the 1.8.0 release.
https://securedrop.org/news/securedrop-workstation-1_9_0-released/
-
SecureDrop Workstation 1.9.0 is now available!
This release hardens the updater against some edge cases discovered during the 1.8.0 release.
https://securedrop.org/news/securedrop-workstation-1_9_0-released/
-
SecureDrop Workstation 1.9.0 is now available!
This release hardens the updater against some edge cases discovered during the 1.8.0 release.
https://securedrop.org/news/securedrop-workstation-1_9_0-released/
-
SecureDrop Workstation 1.9.0 is now available!
This release hardens the updater against some edge cases discovered during the 1.8.0 release.
https://securedrop.org/news/securedrop-workstation-1_9_0-released/
-
@simontatham I guess now I really need to start giving #Qubes OS a try. I understand it isolates clipboard access as well...
> "Qubes prevents clipboard hijacking by using a secure, manual key-combination method to copy text or files between isolated virtual machines."
-
@simontatham I guess now I really need to start giving #Qubes OS a try. I understand it isolates clipboard access as well...
> "Qubes prevents clipboard hijacking by using a secure, manual key-combination method to copy text or files between isolated virtual machines."
-
@simontatham I guess now I really need to start giving #Qubes OS a try. I understand it isolates clipboard access as well...
> "Qubes prevents clipboard hijacking by using a secure, manual key-combination method to copy text or files between isolated virtual machines."
-
@simontatham I guess now I really need to start giving #Qubes OS a try. I understand it isolates clipboard access as well...
> "Qubes prevents clipboard hijacking by using a secure, manual key-combination method to copy text or files between isolated virtual machines."
-
@simontatham I guess now I really need to start giving #Qubes OS a try. I understand it isolates clipboard access as well...
> "Qubes prevents clipboard hijacking by using a secure, manual key-combination method to copy text or files between isolated virtual machines."
-
something i came across looking into distributions to replace debian is the stance that qubes takes on secure boot:
"UEFI Secure Boot is not supported out of the box as UEFI support in Xen is very basic. Arguably secure boot reliance on UEFI integrity is not the best design. [...] See the [Heads project] for a better-designed non-UEFI-based secure boot scheme with very good support for Qubes."
https://doc.qubes-os.org/en/latest/introduction/faq.html#is-secure-boot-supported
alas, i don't think my framework amd laptop (their first-gen amd) supports open firmware...
-
something i came across looking into distributions to replace debian is the stance that qubes takes on secure boot:
"UEFI Secure Boot is not supported out of the box as UEFI support in Xen is very basic. Arguably secure boot reliance on UEFI integrity is not the best design. [...] See the [Heads project] for a better-designed non-UEFI-based secure boot scheme with very good support for Qubes."
https://doc.qubes-os.org/en/latest/introduction/faq.html#is-secure-boot-supported
alas, i don't think my framework amd laptop (their first-gen amd) supports open firmware...
-
something i came across looking into distributions to replace debian is the stance that qubes takes on secure boot:
"UEFI Secure Boot is not supported out of the box as UEFI support in Xen is very basic. Arguably secure boot reliance on UEFI integrity is not the best design. [...] See the [Heads project] for a better-designed non-UEFI-based secure boot scheme with very good support for Qubes."
https://doc.qubes-os.org/en/latest/introduction/faq.html#is-secure-boot-supported
alas, i don't think my framework amd laptop (their first-gen amd) supports open firmware...
-
something i came across looking into distributions to replace debian is the stance that qubes takes on secure boot:
"UEFI Secure Boot is not supported out of the box as UEFI support in Xen is very basic. Arguably secure boot reliance on UEFI integrity is not the best design. [...] See the [Heads project] for a better-designed non-UEFI-based secure boot scheme with very good support for Qubes."
https://doc.qubes-os.org/en/latest/introduction/faq.html#is-secure-boot-supported
alas, i don't think my framework amd laptop (their first-gen amd) supports open firmware...
-
Note to self: how to configure the network manually on #QubesOS AppVM: use
qubesdb-read <path>to read these paths/qubes-ip,/qubes-gateway,/qubes-ip6,/qubes-gateway6. If you can't usequbesdb-readbecause the AppVM has no #Qubes daemons running, you have a bigger problem.
In systemd-networkd, the usual configuration format is:[Match] Name=eth0 [Network] Address=<IPv4> Gateway=<IPv4> Address=<IPv6> Gateway=<IPv6>
But QubesOS AppVMs have IP addresses with /32 or /128 netmasks, I guess it's a basic firewall, so the router is not in the subnet, so systemd-networkd doesn't work. In this case, you need:[Network] Address=<IPv4>/32 Address=<IPv6>/128 [Route] Gateway=<IPv4> GatewayOnLink=yes [Route] Gateway=<IPv6> GatewayOnLink=yes -
Note to self: how to configure the network manually on #QubesOS AppVM: use
qubesdb-read <path>to read these paths/qubes-ip,/qubes-gateway,/qubes-ip6,/qubes-gateway6. If you can't usequbesdb-readbecause the AppVM has no #Qubes daemons running, you have a bigger problem.
In systemd-networkd, the usual configuration format is:[Match] Name=eth0 [Network] Address=<IPv4> Gateway=<IPv4> Address=<IPv6> Gateway=<IPv6>
But QubesOS AppVMs have IP addresses with /32 or /128 netmasks, I guess it's a basic firewall, so the router is not in the subnet, so systemd-networkd doesn't work. In this case, you need:[Network] Address=<IPv4>/32 Address=<IPv6>/128 [Route] Gateway=<IPv4> GatewayOnLink=yes [Route] Gateway=<IPv6> GatewayOnLink=yes -
Note to self: how to configure the network manually on #QubesOS AppVM: use
qubesdb-read <path>to read these paths/qubes-ip,/qubes-gateway,/qubes-ip6,/qubes-gateway6. If you can't usequbesdb-readbecause the AppVM has no #Qubes daemons running, you have a bigger problem.
In systemd-networkd, the usual configuration format is:[Match] Name=eth0 [Network] Address=<IPv4> Gateway=<IPv4> Address=<IPv6> Gateway=<IPv6>
But QubesOS AppVMs have IP addresses with /32 or /128 netmasks, I guess it's a basic firewall, so the router is not in the subnet, so systemd-networkd doesn't work. In this case, you need:[Network] Address=<IPv4>/32 Address=<IPv6>/128 [Route] Gateway=<IPv4> GatewayOnLink=yes [Route] Gateway=<IPv6> GatewayOnLink=yes -
Note to self: how to configure the network manually on #QubesOS AppVM: use
qubesdb-read <path>to read these paths/qubes-ip,/qubes-gateway,/qubes-ip6,/qubes-gateway6. If you can't usequbesdb-readbecause the AppVM has no #Qubes daemons running, you have a bigger problem.
In systemd-networkd, the usual configuration format is:[Match] Name=eth0 [Network] Address=<IPv4> Gateway=<IPv4> Address=<IPv6> Gateway=<IPv6>
But QubesOS AppVMs have IP addresses with /32 or /128 netmasks, I guess it's a basic firewall, so the router is not in the subnet, so systemd-networkd doesn't work. In this case, you need:[Network] Address=<IPv4>/32 Address=<IPv6>/128 [Route] Gateway=<IPv4> GatewayOnLink=yes [Route] Gateway=<IPv6> GatewayOnLink=yes -
does anyone have a link for @micahflee's talk that involved a proof of concept steganographic encrypted OS that hides in the filesystem of another OS? I need it for a blog post I'm writing
#encryption #steganography #qubes -
does anyone have a link for @micahflee's talk that involved a proof of concept steganographic encrypted OS that hides in the filesystem of another OS? I need it for a blog post I'm writing
#encryption #steganography #qubes -
does anyone have a link for @micahflee's talk that involved a proof of concept steganographic encrypted OS that hides in the filesystem of another OS? I need it for a blog post I'm writing
#encryption #steganography #qubes -
does anyone have a link for @micahflee's talk that involved a proof of concept steganographic encrypted OS that hides in the filesystem of another OS? I need it for a blog post I'm writing
#encryption #steganography #qubes -
Huge thanks for hanging out and diving into the Qubes setup and Hacker Summer Camp! Appreciate the chill vibes and Linux gaming chat. Really fun stream! 💻🛡️ #Qubes #Cybersecurity
-
Huge thanks for hanging out and diving into the Qubes setup and Hacker Summer Camp! Appreciate the chill vibes and Linux gaming chat. Really fun stream! 💻🛡️ #Qubes #Cybersecurity
-
Huge thanks for hanging out and diving into the Qubes setup and Hacker Summer Camp! Appreciate the chill vibes and Linux gaming chat. Really fun stream! 💻🛡️ #Qubes #Cybersecurity
-
Huge thanks for hanging out and diving into the Qubes setup and Hacker Summer Camp! Appreciate the chill vibes and Linux gaming chat. Really fun stream! 💻🛡️ #Qubes #Cybersecurity
-
Qubes setup continues! 💻
Join the Hacker Summer Camp watch party – cybersecurity deep dives, rants, chill vibes, and some Linux gaming sprinkled in. Let's build and watch the chaos unfold. 🔴
-
Qubes setup continues! 💻
Join the Hacker Summer Camp watch party – cybersecurity deep dives, rants, chill vibes, and some Linux gaming sprinkled in. Let's build and watch the chaos unfold. 🔴
-
Qubes setup continues! 💻
Join the Hacker Summer Camp watch party – cybersecurity deep dives, rants, chill vibes, and some Linux gaming sprinkled in. Let's build and watch the chaos unfold. 🔴
-
Qubes setup continues! 💻
Join the Hacker Summer Camp watch party – cybersecurity deep dives, rants, chill vibes, and some Linux gaming sprinkled in. Let's build and watch the chaos unfold. 🔴
-
Qubes setup continues! 💻
Join the Hacker Summer Camp watch party – cybersecurity deep dives, rants, chill vibes, and some Linux gaming sprinkled in. Let's build and watch the chaos unfold. 🔴
-
Qubes setup continues! 💻
Join the Hacker Summer Camp watch party – cybersecurity deep dives, rants, chill vibes, and some Linux gaming sprinkled in. Let's build and watch the chaos unfold. 🔴
-
Qubes setup continues! 💻
Join the Hacker Summer Camp watch party – cybersecurity deep dives, rants, chill vibes, and some Linux gaming sprinkled in. Let's build and watch the chaos unfold. 🔴
-
Qubes setup continues! 💻
Join the Hacker Summer Camp watch party – cybersecurity deep dives, rants, chill vibes, and some Linux gaming sprinkled in. Let's build and watch the chaos unfold. 🔴
-
-
-
-
Thanks for chilling with me while I wrestled with Qubes and dove into some Solarpunk vibes! Appreciate the company during the cybersecurity rants and Linux gaming fun. ✌️ #Qubes #Cybersecurity
-
Thanks for chilling with me while I wrestled with Qubes and dove into some Solarpunk vibes! Appreciate the company during the cybersecurity rants and Linux gaming fun. ✌️ #Qubes #Cybersecurity
