Skip to contentSkip to conversation

input/eventX permissions, force feedback

DISCUSSION Anssi Hannula 3 participants 7 messages Jul 18, 2006

lore
Share & tools
lore
#0 lore raw

Currently most distributions have /dev/input/event* strictly as 0600 root:root or 0640 root:root. The user logged in will not have rights to the device, unlike /dev/input/js*, as he could read all passwords from the keyboard device.

This is a problem, because /dev/input/event* is used for force feedback and should therefore be user-accessible.

I can think of the following solutions to this problem:

1. Some creative udev rule to chmod /dev/input/event* less strictly when it has a /dev/input/js* and is thus a gaming device.

2. Some creative udev rule to chmod /dev/input/event* more strictly when it is a keyboard.

3. Have another force feedback interface also in /dev/input/js*.

I prefer the first one, do you think it is a good solution or do you have a better one?

If I go with the first one, what is the preferred way of finding out a gaming device in udev rule?

Signature · 1 line
Anssi Hannula
#1 lore raw

Hi Anssi,

Quoted 10 lines · Anssi Hannula

Currently most distributions have /dev/input/event* strictly as 0600 root:root or 0640 root:root. The user logged in will not have rights to the device, unlike /dev/input/js*, as he could read all passwords from the keyboard device.

This is a problem, because /dev/input/event* is used for force feedback and should therefore be user-accessible.

I can think of the following solutions to this problem:

Quoted 8 lines

1. Some creative udev rule to chmod /dev/input/event* less strictly when it has a /dev/input/js* and is thus a gaming device.

2. Some creative udev rule to chmod /dev/input/event* more strictly when it is a keyboard.

3. Have another force feedback interface also in /dev/input/js*.

You can do it in udev looking either at MODALIAS or at EV and ABS environment variables. I think it is pretty safe to say that a device with EV_ABS, EV_FF, ABS_X and ABS_Y is a force-feedback joystick-type device and not a keyboard.

Another solution would be to relax permissions if user is also console owner (home box installation).

One thing is for sure - I do not like #3 at all ;)

Signature · 1 line
Dmitry
#2 lore raw
Quoted 20 lines · Dmitry Torokhov

Hi Anssi,

Quoted 16 lines · Anssi Hannula

Currently most distributions have /dev/input/event* strictly as 0600 root:root or 0640 root:root. The user logged in will not have rights to the device, unlike /dev/input/js*, as he could read all passwords from the keyboard device.

This is a problem, because /dev/input/event* is used for force feedback and should therefore be user-accessible.

I can think of the following solutions to this problem:

1. Some creative udev rule to chmod /dev/input/event* less strictly when it has a /dev/input/js* and is thus a gaming device.

2. Some creative udev rule to chmod /dev/input/event* more strictly when it is a keyboard.

Quoted 7 lines
Quoted 2 lines

3. Have another force feedback interface also in /dev/input/js*.

You can do it in udev looking either at MODALIAS or at EV and ABS environment variables. I think it is pretty safe to say that a device with EV_ABS, EV_FF, ABS_X and ABS_Y is a force-feedback joystick-type device and not a keyboard.

Okay, thanks. But I think it'd be more consistant if all devices that have js* entries would have the relaxed perms in event*. Looking at joydev.c, that seems to be devices where EV_ABS && (ABS_X || ABS_WHEEL || ABS_THROTTLE) && !(EV_KEY && BTN_TOUCH).

There's another problem, too:
Some distros (Fedora, Mandriva...) don't use groups with /dev/input/jsX, they use pam_console to chmod the device to the console owner. Unfortunately, it allows to specify the permissions based on device file names only.

To solve this problem, I see two solutions:

1. Have the pam_console_apply program extended so that it can perform more complex matches (but what kind of matches would those be?).

2. Have udev create symlinks like the following case:
/dev/input/event3
/dev/input/js0
/dev/input/jsevent0 => event3
Then pam_console_apply could match jsevent[0-9]* and it would follow the symlink, thus chowning event3 to the wanted user.

Unfortunately neither look too good to me. Do you have any other ideas?

Quoted 2 lines

Another solution would be to relax permissions if user is also console owner (home box installation).

I thought of that too, but I thought it's too big a security risk, as it's not guaranteed that somebody else won't temporarily login on another terminal.

Quoted 2 lines

One thing is for sure - I do not like #3 at all ;)

Signature · 1 line
Anssi Hannula
#3 lore raw
Quoted 29 lines · Anssi Hannula
Quoted 20 lines · Dmitry Torokhov

Hi Anssi,

Quoted 16 lines · Anssi Hannula

Currently most distributions have /dev/input/event* strictly as 0600 root:root or 0640 root:root. The user logged in will not have rights to the device, unlike /dev/input/js*, as he could read all passwords from the keyboard device.

This is a problem, because /dev/input/event* is used for force feedback and should therefore be user-accessible.

I can think of the following solutions to this problem:

1. Some creative udev rule to chmod /dev/input/event* less strictly when it has a /dev/input/js* and is thus a gaming device.

2. Some creative udev rule to chmod /dev/input/event* more strictly when it is a keyboard.

Quoted 7 lines
Quoted 2 lines

3. Have another force feedback interface also in /dev/input/js*.

You can do it in udev looking either at MODALIAS or at EV and ABS environment variables. I think it is pretty safe to say that a device with EV_ABS, EV_FF, ABS_X and ABS_Y is a force-feedback joystick-type device and not a keyboard.

Quoted 5 lines

Okay, thanks. But I think it'd be more consistant if all devices that have js* entries would have the relaxed perms in event*. Looking at joydev.c, that seems to be devices where EV_ABS && (ABS_X || ABS_WHEEL || ABS_THROTTLE) && !(EV_KEY && BTN_TOUCH).

OK, you can do that too.

Quoted 11 lines

There's another problem, too:
Some distros (Fedora, Mandriva...) don't use groups with /dev/input/jsX, they use pam_console to chmod the device to the console owner. Unfortunately, it allows to specify the permissions based on device file names only.

To solve this problem, I see two solutions:

1. Have the pam_console_apply program extended so that it can perform more complex matches (but what kind of matches would those be?).

Quoted 9 lines

2. Have udev create symlinks like the following case:
/dev/input/event3
/dev/input/js0
/dev/input/jsevent0 => event3
Then pam_console_apply could match jsevent[0-9]* and it would follow the symlink, thus chowning event3 to the wanted user.

Unfortunately neither look too good to me. Do you have any other ideas?

I think this is really up to particular destribution to decide how they want to handle security/granting access. One could even imagine writing SELinux policies...

Quoted 7 lines
Quoted 2 lines

Another solution would be to relax permissions if user is also console owner (home box installation).

I thought of that too, but I thought it's too big a security risk, as it's not guaranteed that somebody else won't temporarily login on another terminal.

That is what you are doing with pam_console_apply, don't you?

Signature · 1 line
Dmitry
#4 lore raw
Quoted 61 lines · Dmitry Torokhov
Quoted 33 lines · Anssi Hannula
Quoted 6 lines · Dmitry Torokhov

Hi Anssi,

Quoted 2 lines · Anssi Hannula

Currently most distributions have /dev/input/event* strictly as 0600 root:root or 0640 root:root. The user logged in will not have

rights to

Quoted 4 lines
Quoted 4 lines

the device, unlike /dev/input/js*, as he could read all passwords from the keyboard device.

This is a problem, because /dev/input/event* is used for force

feedback

Quoted 5 lines
Quoted 5 lines

and should therefore be user-accessible.

I can think of the following solutions to this problem:

1. Some creative udev rule to chmod /dev/input/event* less strictly

when

Quoted 3 lines
Quoted 3 lines

it has a /dev/input/js* and is thus a gaming device.

2. Some creative udev rule to chmod /dev/input/event* more strictly

when

Quoted 9 lines
Quoted 4 lines

it is a keyboard.

3. Have another force feedback interface also in /dev/input/js*.

You can do it in udev looking either at MODALIAS or at EV and ABS environment variables. I think it is pretty safe to say that a device with EV_ABS, EV_FF, ABS_X and ABS_Y is a force-feedback joystick-type device and not a keyboard.

Quoted 5 lines

Okay, thanks. But I think it'd be more consistant if all devices that have js* entries would have the relaxed perms in event*. Looking at joydev.c, that seems to be devices where EV_ABS && (ABS_X || ABS_WHEEL || ABS_THROTTLE) && !(EV_KEY && BTN_TOUCH).

OK, you can do that too.

Quoted 18 lines

There's another problem, too:
Some distros (Fedora, Mandriva...) don't use groups with /dev/input/jsX, they use pam_console to chmod the device to the console owner. Unfortunately, it allows to specify the permissions based on device file names only.

To solve this problem, I see two solutions:

1. Have the pam_console_apply program extended so that it can perform more complex matches (but what kind of matches would those be?).

2. Have udev create symlinks like the following case:
/dev/input/event3
/dev/input/js0
/dev/input/jsevent0 => event3
Then pam_console_apply could match jsevent[0-9]* and it would follow the symlink, thus chowning event3 to the wanted user.

Quoted 6 lines
Quoted 2 lines

Unfortunately neither look too good to me. Do you have any other ideas?

I think this is really up to particular destribution to decide how they want to handle security/granting access. One could even imagine writing SELinux policies...

Yes, it is. I just asked if you had any better idea or if you were strongly opposed to the solutions I proposed, as I want to make a working solution for my distribution (Mandriva).

Quoted 9 lines
Quoted 7 lines
Quoted 2 lines

Another solution would be to relax permissions if user is also console owner (home box installation).

I thought of that too, but I thought it's too big a security risk, as it's not guaranteed that somebody else won't temporarily login on another terminal.

That is what you are doing with pam_console_apply, don't you?

Yes, but afaics there are currently no device privileges given to the console user which would compromise password security. Providing eventX would do that.

Signature · 1 line
Anssi Hannula
#5 lore raw
In reply to Dmitry Torokhov
Quoted 19 lines · Dmitry Torokhov

Hi Anssi,

Quoted 16 lines · Anssi Hannula

Currently most distributions have /dev/input/event* strictly as 0600 root:root or 0640 root:root. The user logged in will not have rights to the device, unlike /dev/input/js*, as he could read all passwords from the keyboard device.

This is a problem, because /dev/input/event* is used for force feedback and should therefore be user-accessible.

I can think of the following solutions to this problem:

1. Some creative udev rule to chmod /dev/input/event* less strictly when it has a /dev/input/js* and is thus a gaming device.

2. Some creative udev rule to chmod /dev/input/event* more strictly when it is a keyboard.

Quoted 8 lines
Quoted 2 lines

3. Have another force feedback interface also in /dev/input/js*.

You can do it in udev looking either at MODALIAS or at EV and ABS environment variables. I think it is pretty safe to say that a device with EV_ABS, EV_FF, ABS_X and ABS_Y is a force-feedback joystick-type device and not a keyboard.

You could also have udev create specific symlink for such devices, say /dev/input/ff* and make a rule for pam_console to change their permissions. That is finally what is done e.g. for CD-ROMs (cdrom -> hdc/sr0)

-andrey

Quoted 5 lines

Another solution would be to relax permissions if user is also console owner (home box installation).

One thing is for sure - I do not like #3 at all ;)

#6 lore raw
Quoted 33 lines · Andrey Borzenkov
Quoted 20 lines · Dmitry Torokhov

Hi Anssi,

Quoted 16 lines · Anssi Hannula

Currently most distributions have /dev/input/event* strictly as 0600 root:root or 0640 root:root. The user logged in will not have rights to the device, unlike /dev/input/js*, as he could read all passwords from the keyboard device.

This is a problem, because /dev/input/event* is used for force feedback and should therefore be user-accessible.

I can think of the following solutions to this problem:

1. Some creative udev rule to chmod /dev/input/event* less strictly when it has a /dev/input/js* and is thus a gaming device.

2. Some creative udev rule to chmod /dev/input/event* more strictly when it is a keyboard.

Quoted 8 lines
Quoted 2 lines

3. Have another force feedback interface also in /dev/input/js*.

You can do it in udev looking either at MODALIAS or at EV and ABS environment variables. I think it is pretty safe to say that a device with EV_ABS, EV_FF, ABS_X and ABS_Y is a force-feedback joystick-type device and not a keyboard.

Quoted 4 lines

You could also have udev create specific symlink for such devices, say /dev/input/ff* and make a rule for pam_console to change their permissions. That is finally what is done e.g. for CD-ROMs (cdrom -> hdc/sr0)

Yes, I proposed this kind of solution too in a later post :)

Quoted 9 lines
Quoted 7 lines

Another solution would be to relax permissions if user is also console owner (home box installation).

One thing is for sure - I do not like #3 at all ;)

Signature · 1 line
Anssi Hannula