[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#879715: marked as done (ITP: usbauth -- USB firewall against BadUSB attacks)

Your message dated Mon, 6 Nov 2017 18:24:57 +0100
with message-id <2e6c13b1-1eb4-a7e6-24b6-19cf26deec03@gmail.com>
and subject line Re: Bug#879715: Acknowledgement (ITP: usbauth -- USB firewall against BadUSB attacks)
has caused the Debian Bug report #879715,
regarding ITP: usbauth -- USB firewall against BadUSB attacks
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
879715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879715
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Stefan Koch <stefan.koch10@gmail.com>

* Package name    : usbauth
  Version         : 1.0
  Upstream Author : Stefan Koch <stefan.koch10@gmail.com>
* URL             : https://github.com/kochstefan/usbauth-all/usbauth
* License         : GPL-2.0
  Programming Lang: C
  Description     : USB firewall against BadUSB attacks

It is a firewall against BadUSB attacks. A config file descibes in which way USB interfaces would be accepted or denied.
To the kernel an interface authorization was developed with this firewall.
The firewall sets the authorization mask according to the rules.

This work was initially created for SUSE in 2015. Part of it was the USB interface authorization for the Linux kernel. It's contained in Linux since kernel version 4.4.

Please add the packages libusbauth-configparser, usbauth, usbauth-notifier to debian unstable.

See also: openSUSE package request (https://build.opensuse.org/request/show/533513)

--- End Message ---
--- Begin Message --- 
#880983 replaces this bug report.

--- End Message ---
Reply to: