1Password and the unlock file. Is anyone using this?

  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

What you're inclined to call a file, they are not. (As they wrote the software, I'm going to go with them on this.) They're intentionally vague about how they store it or where.


the Secret Key is stored securely on your devices, it’s not something you need to enter every time you unlock 1Password.


From: https://1passwordstatic.com/files/security/1password-white-paper.pdf

Locally exposed Secret Keys

Once a client is enrolled, it will store a copy of the Secret Key on the local device. Because the Secret Key must be used to derive the user’s AUK it cannot be encrypted by the same AUK or by any key that is directly or indirectly encrypted with the AUK. Depending on client and client platform the Secret Key may[3] be stored on the device using some of the protections offered by the operating system and may be lightly obfuscated. However, it should be assumed that an attacker who gains read access to the user’s disk will acquire the Secret Key.

[3] We are deliberately vague about this, as practice may change rapidly from version to version, including different behaviors on different operating system versions.