Export thread

  • DNS Benchmark v2 Release 5 with Consultant License
    Guest:
    If you own any earlier release of our DNS Benchmark you may immediately download its release #5 replacement. Running an earlier release will detect the new release and help you upgrade.

    Although this release is cosmetic, appearance matters and affects ease of use. The biggest change, as seen in the image above, is that the DNS Benchmark now has a traditional Windows application menu to more fully expose its many features. This release is also "Consultant License Aware" and GRC will now issue a Consultant version when owners have previously purchased four "Personal Use" licenses. If you have previously purchased four DNSB licenses, or if you wish to upgrade your "Personal Use" license to Consultant, GRC's purchase process will direct you through that process.
    /Steve.
  • 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.)

While passkeys are not ready: Yubikey for OTP

#1

brasilik

brasilik

Hey @Steve and audience,

After the recent discussions around passkeys on the podcast, I wanted to share and get feedback on my approach.

As many other listeners, I also have a Yubikey at home and one with me.
But I have never stored a passkey on them. I use the Yubikey Authenticator app for iOS to store OTP secrets on the keys. I always set up both keys at the same time for any service.

Passwords are stored in Bitwarden, Bitwarden is secured by OTP codes from the Yubikeys as well.

With the almost universal availability is OTP, this is a pragmatic way that I have found to secure my accounts by something “physical”.
The Yubikey I carry has also set a password for additional security.

Any downsides to this approach that I might be missing not seeing?


The process in detail below:

Setup of OTP:
1. Ask the site for an OTP qrcode
2. Stick Yubikey A into the phone and scan the code with the Yubikey Authenticator App
3. Stick Yubikey B into the phone and scan the code with the Yubikey Authenticator App
4. Geberate an OTP from either key and put it in the site for confirmation

Get an OTP
1. Stick the Yubikey into the phone
2. Open Yubikey Authenticator App
3. Generate a code an put it in



Happy for any feedback and love the show


#2

P

PHolder

Well the possible downside is any weakness in the Yubikey Authenticator App. Depending on how it's coded, it might be possible to bypass the requirement for the key. It's clearly storing its data on the phone, not on the key, so it may be that it merely checks for the existence of the key before decoding the data on the phone. (I would need to know more about the design of the app.)


#3

brasilik

brasilik

PHolder said:
Well the possible downside is any weakness in the Yubikey Authenticator App. Depending on how it's coded, it might be possible to bypass the requirement for the key. It's clearly storing its data on the phone, not on the key, so it may be that it merely checks for the existence of the key before decoding the data on the phone. (I would need to know more about the design of the app.)
Click to expand...
Yea, true about possible vulnerabilities in the app.

It’s not storing anything in there tho. It’s all on the key, which of course is important if I loose my phone. I verified that by using it from a second phone and works great


#4

P

PHolder

brasilik said:
using it from a second phone and works great
Click to expand...
Oh, okay then. I guess it must be storing the OTP seeds on the key, which is safer (shouldn't suffer the issue I thought it had above), but should have limits to how many it can store. Do you know the limits?


#5

brasilik

brasilik

PHolder said:
Oh, okay then. I guess it must be storing the OTP seeds on the key, which is safer (shouldn't suffer the issue I thought it had above), but should have limits to how many it can store. Do you know the limits?
Click to expand...
I was not able to find the limits. If I am not mistaken, this is the doc: https://developers.yubico.com/OATH/

My best guess is that it takes up one of the 20 slots the Yubikey 4 and 5 have.

I am not affected by it, as I only store crucial second factors there: Bitwarden and email.

For most other services, I store them in Bitwarden


Top Bottom
Back