Yubico Forum

Re: [S!] Administrator rights required to detect Yubikey on

2015-04-14T18:14:48+01:00

Would appreciate getting the source code, so I can build it myself instead of running unknown apps..

Also, download link is dead.

Statistics: Posted by advance — Tue Apr 14, 2015 6:14 pm

Re: [S!] Administrator rights required to detect Yubikey on

2015-04-10T11:17:39+01:00

advance wrote:

Are you sure you aren't running your apps using an Admin account?

Yes, I also tested limited Guest accounts and they were able to communicate with the Yubikey.

I made this application to see what error codes you're getting and also show some paths that you might need later when checking the driver or symbolic link permissions:

Please reply with any error codes (other than Vendor Mismatch)

YubiKeyDeviceDetect.zip

Statistics: Posted by dmex — Fri Apr 10, 2015 11:17 am

Re: [S!] Administrator rights required to detect Yubikey on

2015-04-06T02:32:36+01:00

Windows 8.1, no security software, no USB hub, no Yubikey accessing application except for Yubikey Personalization Tool and PasswordSafe 3.35.

Didn't have to install any kind of driver, iirc.

Are you sure you aren't running your apps using an Admin account?

Statistics: Posted by advance — Mon Apr 06, 2015 2:32 am

Re: [S!] Administrator rights required to detect Yubikey on

2015-04-04T14:07:15+01:00

advance wrote:

Can you someone explain to me why the Yubikey NEO cannot be accessed by programs with non-admin rights?

It works fine here using non-administrative applications (including applications I've written myself).

It might help to give details about your computer setup, what security software are you using, do you use a USB hub and/or do you use yubikey applications such as the logon administration tool?

Statistics: Posted by dmex — Sat Apr 04, 2015 2:07 pm

Re: [S!] Administrator rights required to detect Yubikey on

2015-03-31T19:55:23+01:00

I have the exact same issue.

Even worse - PasswordSafe 3.35 also requires administrator rights to access the Yubikey.

The end result is that to open PasswordSafe, I need to:

1. Execute PasswordSafe.
2. Click "Yes" in the Run As Admin? message box.
3. Type in my password.
4. Click the Yubikey button in PasswordSafe.
5. Click the physical button on my Yubikey NEO.

This is simply insane. Way too many steps.

Not to mention that running PasswordSafe (or any other program that doesn't need admin rights) as administrator is simply a bad idea.

What's the problem? Can you someone explain to me why the Yubikey NEO cannot be accessed by programs with non-admin rights?

Thanks,

Alon

Statistics: Posted by advance — Tue Mar 31, 2015 7:55 pm

Re: [BUG] No yubi tools detect my new neo. Need administrat

2015-02-23T11:49:54+01:00

Right click on the files in the folder, windows may mark these file coming from the Internet to require admin rights to be executed.

This is a configuration on your machine, not depending on the software you downloaded.

see screenshot
Unblock file.png

Statistics: Posted by Tom2 — Mon Feb 23, 2015 11:49 am

Re: [QUESTION] No yubi tools detect my new neo.

2015-02-23T02:33:32+01:00

Apparently the problem is that none of the yubico tools request administrator permissions when they need them. This is no longer a question, but a bug. I'll edit the tag appropriately.

Statistics: Posted by aarcane — Mon Feb 23, 2015 2:33 am

[S!] Administrator rights required to detect Yubikey on Win

2015-02-23T02:35:36+01:00

I purchased a new YubiKey Neo for $50 on Amazon, and I can connect it to my laptop and use it for both U2F and OTP authentication, but if I try to type ykinfo -v to show the version information as per this guide ( https://www.yubico.com/2012/12/yubikey-neo-openpgp/ ) or if I download Yubikey Personalization Tool, both show No YubiKey Inserted or similar error messages. I'm unable to proceed to enabling openpgp authentication with this yubikey, which was the primary purpose for which I bought it. PLease advice me on how to proceed.

As posted in a followup, I have to manually run as administrator to get this to work. Unfortunately, nearly every windows application released in the last decade can request administrator permission if needed at launch time. This is a bug, and is unacceptable behavior in this day and age.

Statistics: Posted by aarcane — Mon Feb 23, 2015 1:52 am