Jump to content

Krypton

Administrator
  • Posts

    5420
  • Joined

  • Days Won

    163
  • csCoins

    8,047,998 [ Donate ]

Everything posted by Krypton

  1. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  2. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  3. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  4. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  5. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  6. Wichtig ist dass das Ende der vorletzten „Coin“ wallet eine brandneue ist (COLD). Ebenfalls: Zeit Korrelation vermeiden.
  7. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  8. Herzlich Willkommen! Bitte beachte diese Regel: §7.4 - Verkaufsregeln: Verkäufe sind nicht limitiert, und es besteht keine Vendorenpflicht außer für Externe Seiten!
  9. OpSec-Buch — Zusammenfassung Thema: Anfänger-Anleitung für einen Privacy-Stack mit Linux, VMs und Double-VPN. Setup-Kern: - Host: Fedora KDE mit LUKS-Verschlüsselung, Firewall auf drop, SELinux enforcing, MAC-Randomisierung. - VPN A am Host: Mullvad mit Multi-Hop und Lockdown-Mode. - Work-VM in KVM/virt-manager, ebenfalls LUKS-verschlüsselt, andere Zeitzone (UTC), eigener User. - VPN B in der VM: IVPN (andere Firma + Jurisdiction) mit Kill-Switch — ergibt Tunnel-im-Tunnel, 4 Hops. - VM-Disks in Veracrypt-Container (Mount-on-demand, optional Hidden Volume). - Optional: Whonix-VM für Tor, separate Messaging-VM für Signal/SimpleX/XMPP. Threat-Modelle: Privacy-User (Standard) / Journalist (komplett + Routine) / Aktivist (+ Tails, anonyme Hardware, Gateway-VM Pflicht). Workflow: Snapshots vor jeder Session, danach zurückrollen — keine Persistence von Cookies/Fingerprints. Identitäten strikt trennen, eine pro VM. Wichtige Regeln: Boot-Reihenfolge Host→VPN A→VM→VPN B→Leak-Test, niemals Identitäten mischen, Zahlungen anonym (Crypto/Cash), keine echten Namen in Filenames, Host sauber halten. Häufige Fehler: DNS-/IPv6-/WebRTC-Leaks, Zeitzonen-Korrelation, Zahlungsspuren, SELinux nicht enforcing, Social-Graph-Überlappung. Abgrenzung: Kein Qubes-Ersatz, sondern pragmatischer Kompromiss zwischen Sicherheit und Daily-Driver-Tauglichkeit. Kernsatz: Sicherheit ist Routine, nicht Setup.
  10. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  11. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  12. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  13. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  14. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  15. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  16. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  17. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  18. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  19. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  20. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  21. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  22. This topic is protected by a password!
    You must enter the correct topic password to gain access to this topic. Please ensure that your browser is capable of storing temporary cookies.
  23. DafĂĽr sorgen wir.
Ă—
Ă—
  • Create New...