Bug 1472188 - pam_usb: package missing default config file
Summary: pam_usb: package missing default config file
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pam_usb
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Francisco Javier Tsao Santín
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-18 08:56 UTC by Vasiliy Glazov
Modified: 2017-07-18 10:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-18 10:38:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vasiliy Glazov 2017-07-18 08:56:41 UTC
Description of problem:
This package not contain default config file /etc/pamusb.conf

Version-Release number of selected component (if applicable):
pam_usb-0.5.0-2


$ sudo pamusb-conf --add-device sample
Please select the device you wish to add.
* Using "ADATA USB Flash Drive (00000003AABBFA)" (only option)

Which volume would you like to use for storing data ?
* Using "/dev/sdg1 (UUID: ECF0-6724)" (only option)

Name            : sample
Vendor          : ADATA
Model           : USB Flash Drive
Serial          : 00000003AABBFA
UUID            : ECF0-6724

Save to /etc/pamusb.conf ?
[Y/n] y
Unable to read /etc/pamusb.conf: [Errno 2] No such file or directory: '/etc/pamusb.conf'


Even after touch /etc/pamusb.conf it can't be used:

Save to /etc/pamusb.conf ?
[Y/n] y
Unable to read /etc/pamusb.conf: no element found: line 1, column 0

Adding sample file from git repo solving problem.

Comment 1 Francisco Javier Tsao Santín 2017-07-18 10:14:51 UTC
The default config file is in /etc/security/pamusb.conf. I moved there because I think is more appropiate to be there with other pam configs.

Comment 2 Vasiliy Glazov 2017-07-18 10:38:46 UTC
OK, I did not see it first.

But pamusb-conf use /etc/pamusb.conf by default. I am think it need to be cleared (moved back or simlinked) so users did not fall into this situation.

Comment 3 Francisco Javier Tsao Santín 2017-07-18 10:54:50 UTC
That's right. I'll issue a patch.


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