Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36961 - [sshguard] whitelist feature

Attached to Project: Community Packages
Opened by Jim Casteel (skunark) - Tuesday, 17 September 2013, 05:35 GMT
Last edited by Balló György (City-busz) - Thursday, 20 February 2014, 19:08 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Massimiliano Torromeo (mtorromeo)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Enable whitelist file feature for sshguard

Additional info:
use the "-w" switch with path to file, for example:
-w /etc/hosts.allow

This task depends upon

Closed by  Balló György (City-busz)
Thursday, 20 February 2014, 19:08 GMT
Reason for closing:  Won't implement
Comment by Massimiliano Torromeo (mtorromeo) - Wednesday, 30 October 2013, 18:25 GMT
I've changed the script to accept any additional options for sshguard. You have to use your own service file for this.
Comment by Jim Casteel (skunark) - Monday, 11 November 2013, 11:36 GMT
  • Field changed: Percent Complete (100% → 0%)
Solution doesn't address the problem since you still have to still have to modify the service file. Probably better to reject feature request or provide the whitelist file w/wo alternate service file.

Solution isn't exactly reliable either. If a whitelist file was used, it could be troublesome if package updates removes option. (basic reason behind feature request)
Comment by Massimiliano Torromeo (mtorromeo) - Monday, 11 November 2013, 11:40 GMT
The solution is valid because it addresses a problem that wouldn't have allowed for the options to be passed to the sshguard-journalctl script.

Service files are meant to be modified by the user when the startup has to be customized, this was never considered an issue.
Comment by Balló György (City-busz) - Thursday, 20 February 2014, 19:07 GMT
You can customize the systemd unit file for your own needs as it described here:
https://wiki.archlinux.org/index.php/Systemd#Editing_provided_unit_files

Loading...