Bug 499997 - Policy for fingerprint authentication is wrong
Policy for fingerprint authentication is wrong
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-09 19:05 EDT by Patrick
Modified: 2009-05-11 08:07 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-05-11 08:07:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Policy file for fprint (371 bytes, text/plain)
2009-05-09 19:05 EDT, Patrick
no flags Details
Second policy file for fprint (74 bytes, text/plain)
2009-05-09 19:07 EDT, Patrick
no flags Details

  None (edit)
Description Patrick 2009-05-09 19:05:37 EDT
Created attachment 343240 [details]
Policy file for fprint

Description of problem:
There are errors in the policy for fprintd (fingerprint authentication)

Version-Release number of selected component (if applicable):
selinux-policy-3.6.12-28.fc11.noarch

How reproducible:
Try to login with the fingerprint reader is use fprintd-verify <user>. It always fails

Steps to Reproduce:
1. enable fingerprint authentication
2. submit right index finger fingerprint
3. try to login with right index finger or use fprintd-verify
  
Actual results:
Fail

Expected results:
Login succeeds or fprintd-verify gives a match

Additional info:
The content of the attached policy files was given to me by dgrift in #fedora-selinux. They solved the errors.
Comment 1 Patrick 2009-05-09 19:07:06 EDT
Created attachment 343241 [details]
Second policy file for fprint
Comment 2 Daniel Walsh 2009-05-11 08:07:07 EDT
Fixed in selinux-policy-3.6.12-33.fc11.noarch

Note You need to log in before you can comment on or make changes to this bug.