First Last Prev Next    This bug is not in your last search results.
Bug 40815 - Using fail2ban to stop locky-style mass file modifications on shares
Using fail2ban to stop locky-style mass file modifications on shares
Status: RESOLVED MOVED
Product: Z_wiki.univention.de
Classification: Unclassified
Component: Cool Solutions - other
unspecified
Other Linux
: P3 normal
: ---
Assigned To: Bugzilla Mailingliste
http://www.heise.de/security/artikel/...
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-03-02 11:31 CET by Arvid Requate
Modified: 2016-09-21 18:10 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Security Issue
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Security
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2016-03-02 11:31:31 CET 
We should describe how to configure Samba and fail2ban to detect and stop locky-style mass file modifications on Samba file shares. See URL for an article describing that approach.
Comment 1 Michel Smidt 2016-06-16 14:15:20 CEST 
Moved to redmine #5457.
First Last Prev Next    This bug is not in your last search results.