aboutsummaryrefslogtreecommitdiff
path: root/security/fprint_demo
diff options
context:
space:
mode:
authorSimon Barner <barner@FreeBSD.org>2008-07-31 20:35:48 +0000
committerSimon Barner <barner@FreeBSD.org>2008-07-31 20:35:48 +0000
commit2231390069ff40d14e3f5c1fe7fcf4240b63edd5 (patch)
treefd1cefe6e8965d3d4ce0b5e7f68f303a378a777e /security/fprint_demo
parent83ad0a632205617097eae3f2b7ac2e1c0b2954f8 (diff)
downloadports-2231390069ff40d14e3f5c1fe7fcf4240b63edd5.tar.gz
ports-2231390069ff40d14e3f5c1fe7fcf4240b63edd5.zip
Notes
Diffstat (limited to 'security/fprint_demo')
-rw-r--r--security/fprint_demo/pkg-message5
1 files changed, 4 insertions, 1 deletions
diff --git a/security/fprint_demo/pkg-message b/security/fprint_demo/pkg-message
index 14cbc92b49aa..aa5c8ce097e4 100644
--- a/security/fprint_demo/pkg-message
+++ b/security/fprint_demo/pkg-message
@@ -1,10 +1,12 @@
In order to enroll new finger prints, you must have r/w access to the
-usb device node(s) of your finger print reader (e.g. /dev/ugen*)
+usb device node(s) of your finger print reader (i.e., /dev/{ugen, usb}*)
(tested with UPEK finger print reader as found in Lenovo T61).
It is recommended to use devfs.rules(5) and a dedicated group to manage
access to your finger print reader.
+You can use `usbdevs -v' to see if your sensor is accessible.
+
Example configuration:
- /etc/rc.conf:
devfs_system_ruleset="localrules"
@@ -12,5 +14,6 @@ devfs_system_ruleset="localrules"
- /etc/devfs.rules:
[localrules=10]
add path 'ugen0*' mode 0660 group operator
+add path 'usb0*' mode 0660 group operator
# /etc/rc.d/devfs restart