User Activity

  • Posted a comment on discussion Feature requests on VeraCrypt

    it might be nice to have a way to have multiple methods that could decrypt the volume independently, e.g. to have a password/keyfile/security token or whatever for "general use", and a "backup key" of sorts if anything fails. in bitlocker for example you have the ability to have several different encryption methods but near-always you have a 48-digit recovery key for e.g. if the TPM fails. in LUKS you also have keyslots you can basically fill with whatever your imagination (and the one of the programmers)...

  • Modified a comment on discussion Feature requests on VeraCrypt

    ups doppelt - bitte löschhen oops this went double please delete.

  • Posted a comment on discussion Feature requests on VeraCrypt

    so einfach ist es nicht. die Zeichen sind am Ende auch nur Bytefolgen und bestehen aus nullen und einsen. und am ende wird die Zeichenkette einfach nur in nen Mixer aus verdammit Viel Mathe geworfen und fertig ist der Key zum entschlüsseln. wie sollte ein "Eigenes Zeichen" überhaupt technisch aussehen.

  • Posted a comment on discussion Feature requests on VeraCrypt

    so einfach ist es nicht. die Zeichen sind am Ende auch nur Bytefolgen und bestehen aus nullen und einsen. und am ende wird die Zeichenkette einfach nur in nen Mixer aus verdammit Viel Mathe geworfen und fertig ist der Key zum entschlüsseln. wie sollte ein "Eigenes Zeichen" überhaupt technisch aussehen.

  • Posted a comment on discussion Feature requests on VeraCrypt

    considering how last time I checked veracrypt doesnt really have a concept of a backup key like a second password or keyfile or whatever you could use instead of what you normally use this seems like a big issue in terms of data loss. ocrypt apparently has 2 things that can be a real issue here: 1) it relies on servers that if ever gone or inaccessible, your hash goes toast 2) if an attacker wastes your pin attempts, your hash goes toast as the servers will deny further attempts therefore this would...

  • Created ticket #130 on Snappy Driver Installer

    Unsigned driver not marked properly

  • Posted a comment on discussion Feature requests on VeraCrypt

    I have to agree that this would be awesome. I have dont this a ton of times when I used Bitlocker in the past, to get my reboots done remotely. imo this should be only done for a reboot and with prior activation, and after the reboot has finished, wipe the password from whereever it was stored and if the user wants, inform him. also in case of systems with TPMs a temp key could be placed there that would be valid for just that reboot. after that it would be invalidated and removed from the TPM.

View All

Personal Data

Username:
my1xt
Joined:
2018-02-21 14:07:00

Projects

  • No projects to display.

Personal Tools