Yubico Forum

Re: alternative keyboard layout support

2013-10-21T16:22:51+01:00

Udev rules didn't helped me, but solution from haavardm fixed the problem, at least on the client side.

viewtopic.php?f=16&t=317&hilit=dvorak&start=10#p2399

Quote:

For those using X11 >= 1.7.99.901-1, put the following in /etc/X11/xorg.conf to have the yubikey get a us keyboard layout regardless of what layout you normally have:

Code:

Section "InputClass"
  Identifier      "yubikey"
  MatchVendor "Yubico"
  MatchProduct "Yubikey"
  Option "XkbModel" "pc101"
  Option "XkbLayout" "us"
  Option "XkbVariant" "intl"
EndSection

Statistics: Posted by trilliput — Mon Oct 21, 2013 4:22 pm

Re: alternative keyboard layout support

2013-03-21T13:50:09+01:00

Hello,

This is how you can achieve having all YubiKeys inserted mapped to qwerty layout:

* Add /etc/default/qwerty.keyboard

Code:

XKBMODEL="pc101"
XKBLAYOUT="us"
XKBVARIANT="qwerty"
XKBOPTIONS=""

* Add /etc/udev/rules.d/99-yubikey_qwerty.rule

Code:

ACTION=="add|change", SUBSYSTEM=="input", \
       ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0010|0110|0111", \
       IMPORT{file}="/etc/default/qwerty.keyboard"

* Reboot

/klas

Statistics: Posted by Klas — Thu Mar 21, 2013 1:50 pm

Re: alternative keyboard layout support

2013-03-19T16:35:57+01:00

Hi, I just got my standard yubikey, and I'm trying to get my system to recognize it as a US/qwerty keyboard. I normally type in dvorak. This way, even the static passwords would be correct on my laptop and when I move to other computers that use qwerty layouts.

I tried using the code that haavardm posted in xorg.conf, but it doesn't seem to work for me. I'm running kubuntu 12.10. This is the output of setxkbkmap:

Code:

$ setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules:      evdev
model:      pc101
layout:     us,us
variant:    dvorak,
options:    terminate:ctrl_alt_bksp
Trying to build keymap using the following components:
keycodes:   evdev+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc+us(dvorak)+us:2+inet(evdev)+terminate(ctrl_alt_bksp)
geometry:   pc(pc101)
xkb_keymap {
        xkb_keycodes  { include "evdev+aliases(qwerty)" };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc+us(dvorak)+us:2+inet(evdev)+terminate(ctrl_alt_bksp)"       };
        xkb_geometry  { include "pc(pc101)"     };
};

Is there anyway to specify so that X would know that the keyboard of my laptop is Dvorak and the yubikey is querty?

It doesn't seem like I have such options in KDE's keyboard layout options.

Any help would be appreciated!

Statistics: Posted by kychen — Tue Mar 19, 2013 4:35 pm

Re: alternative keyboard layout support

2013-02-26T21:56:51+01:00

The Yubikey NEO does support configuration of a custom key map to address this and similar issues.

Best regards,

JakobE
Hardware- and firmware guy @ Yubico

Statistics: Posted by Jakob — Tue Feb 26, 2013 9:56 pm

Re: alternative keyboard layout support

2013-02-25T20:59:53+01:00

I've just submited the same problem to the support team.

I'm using the BEPO layout (which is the french equivalent to DVORAK), and unfortunately it's not possible to use my Yubikey when this layout is activated. That's a real shame, especially considering the Yubikey is used by both end-users and technology enthousiasts/powerusers.

I hope this issue will be resolved soon.

Statistics: Posted by fbnlsr — Mon Feb 25, 2013 8:59 pm

Re: alternative keyboard layout support

2012-04-14T08:20:52+01:00

Three years after this topic has been started the problem hasn't been solved yet? Just bought my first key and using dvorak the key is almost unusable with this restriction.

The excitement quickly turned into disappointment having wasted $36. This is definitely something you should warn your customers about before letting them order.

Statistics: Posted by sebastian — Sat Apr 14, 2012 8:20 am

Re: alternative keyboard layout support

2011-06-29T20:35:59+01:00

Isn't there a way to use udev and xorg.conf file to get ubikey seen as qwerty keyboard whatever layout used by user?
Of course this should be useful only for Linux system.

Sorry for my bad English I don't speak it very often.

Statistics: Posted by lordphoenix — Wed Jun 29, 2011 8:35 pm

Re: alternative keyboard layout support

2011-06-02T23:40:23+01:00

Couldn't you just integrate dholth's code into the main server and then this problem would be solved? That seems the easiest and best solution. Switching back and forth is annoying

Statistics: Posted by singpolyma — Thu Jun 02, 2011 11:40 pm

Re: alternative keyboard layout support

2010-10-30T00:19:32+01:00

We have the option of sending all modhex characters first by setting the CFGFLAG_SEND_REF flag during configuration. Then, the string "cbdefghijklnrtuv" is sent first in all OTP outputs.

Regards,

JakobE
Hardware- and firmware guy @Yubico

Statistics: Posted by Jakob — Sat Oct 30, 2010 12:19 am

Re: alternative keyboard layout support

2010-10-24T07:55:26+01:00

The "language prefix" approach has been thought of long ago, but just makes the entry time even longer.

When making AuthLite we did some calculation and it turns out to be VERY easy to discern Dvorak vs Qwerty with a high level of confidence. There are some very unlikely cases where an OTP could be either language. In these cases we have chosen to ASSUME qwerty. One could also try qwerty first and fail over to dvorak and try again with that.

It seriously took us like, one day to figure all this out in AuthLite and build it in. But that's because I am a dvorak user so any product I work on had better support it

Statistics: Posted by ferrix — Sun Oct 24, 2010 7:55 am

Re: alternative keyboard layout support

2010-10-23T21:18:46+01:00

A bit late late to the discussion, but to throw in my 2 cents; wouldn't the easiest be to just prepend each OTP with each of the modhex characters? That way you can read which character in the current keymap represents each modhex character?

Statistics: Posted by haavardm — Sat Oct 23, 2010 9:18 pm

Re: alternative keyboard layout support

2010-10-23T21:14:45+01:00

For those using X11 >= 1.7.99.901-1, put the following in /etc/X11/xorg.conf to have the yubikey get a us keyboard layout regardless of what layout you normally have:

Code:

Section "InputClass"
  Identifier      "yubikey"
  MatchVendor "Yubico"
  MatchProduct "Yubikey"
  Option "XkbModel" "pc101"
  Option "XkbLayout" "us"
  Option "XkbVariant" "intl"
EndSection

Statistics: Posted by haavardm — Sat Oct 23, 2010 9:14 pm

Re: alternative keyboard layout support

2010-02-09T13:55:59+01:00

I moved my keyboard layout translation software to http://bitbucket.org/dholth/yubikey/ . It takes a Yubikey OTP from almost any keyboard layout and spits out the possible modhex translations. There is usually only one possibility but occasionally there are a couple of possibilities. The JavaScript version is still demoed at http://dingoskidneys.com/~dholth/yubikey/

The source includes the JavaScript version, a PHP version that could basically replace the "is this a valid yubikey" regex inside the server, a Python version, and some other stuff. If you're running your own validation server you might want to check it out.

Statistics: Posted by dholth — Tue Feb 09, 2010 1:55 pm

Re: alternative keyboard layout support

2010-01-27T00:14:37+01:00

Sorry for keeping all Dvorak guys on the hook in this matter. We've been evaluating several options for not just supporting Dvorak keyboards but also other languages. Given the overall complexity of of the task, it has been somewhat dangling. I hope we'll be able to present a good solution meeting the needs later this spring. That's the best guess for now.

With the best regards,

JakobE
Hardware- and firmware guy @ Yubico

Statistics: Posted by Jakob — Wed Jan 27, 2010 12:14 am

Re: alternative keyboard layout support

2010-01-25T21:09:22+01:00

Has there been any progress on getting this integrated into the validation server? As a Dvorak user and new YubiKey owner, it just took me a good hour to figure out that I needed to switch back into QWERTY for my YubiKey to work. I was in the middle of explaining the problem in a support email when the light bulb finally went off

Statistics: Posted by dstrelau — Mon Jan 25, 2010 9:09 pm