Bug 43519 – FANotify Kernelinterface

Bug 43519 - FANotify Kernelinterface


Summary:	FANotify Kernelinterface

Status:	CLOSED WORKSFORME

Product:	UCS
Classification:	Unclassified
Component:	Kernel
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 4.2
Assigned To:	Philipp Hahn
QA Contact:	Stefan Gohmann

URL:
Keywords:	interim-3

Depends on:	42048
Blocks:
	Show dependency tree / graph

Reported:	2017-02-09 12:30 CET by Jens Thorp-Hansen
Modified:	2017-04-04 18:28 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Feature Request
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?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017020821000171
Bug group (optional):
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 Jens Thorp-Hansen

2017-02-09 12:30:20 CET

Virus scanner may use the FANotify Kernelinterface to do on-access scans, however UCS does not support this at the moment. Can the support be added?

Comment 1 Philipp Hahn

2017-02-09 12:47:53 CET

Current linux-4.1 kernel in UCS-4.1 already has read support, UCS-4.2 will have the functionality to block processes with linux-4.9:
# zgrep FANOTIFY /boot/config-4.*
/boot/config-4.1.0-ucs222-amd64:CONFIG_FANOTIFY=y
/boot/config-4.1.0-ucs222-amd64:# CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set
/boot/config-4.9.0-ucs102-amd64:CONFIG_FANOTIFY=y
/boot/config-4.9.0-ucs102-amd64:CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y

Comment 2 Stefan Gohmann

2017-03-06 06:53:05 CET

OK

Comment 3 Stefan Gohmann

2017-04-04 18:28:56 CEST

UCS 4.2 has been released:
 https://docs.software-univention.de/release-notes-4.2-0-en.html
 https://docs.software-univention.de/release-notes-4.2-0-de.html

If this error occurs again, please use "Clone This Bug".