[Bug 219408] [NEW PORT] security/sedutil Self Encrypting Drive utility
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri May 19 20:47:40 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219408
Bug ID: 219408
Summary: [NEW PORT] security/sedutil Self Encrypting Drive
utility
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: ken at FreeBSD.org
Created attachment 182746
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182746&action=edit
sedutil port shar archive
This is a port of sedutil, a Self Encrypting Drive utility. This allows users
to manage drives with SED functionality based on the various TCG (Trusted
Computing Group) standards.
Alexander Motin ported it to FreeBSD, and I have added a number of bug fixes.
The utility maintainers have not yet incorporated Alexander's or my changes,
thus the port pulls from my GitHub account.
This port passes portlint, but I haven't tested it to make sure it builds on
all architectures, etc.
>From the web site:
The Drive Trust Alliance software (sedutil) is an Open Source (GPLv3)
effort to make Self Encrypting Drive technology freely available to
everyone. It is a combination of the two known available Open Source code
bases today: msed and OpalTool.
The DTA Open Source can be employed freely not only for higher security
applications but also for integration in embedded applications such as
Automotive, Aerospace, Home Automation, and everywhere where the Data
Leakage problem has already become obvious and where it will be obvious.
The storage device suppliers are already gearing to give you
self-encrypting storage. All you have to do is work with them.
Original utility GitHub page:
https://github.com/Drive-Trust-Alliance/sedutil
Alexander Motin's FreeBSD changes:
https://github.com/amotin/sedutil
Alexander's and my changes combined:
https://github.com/kendmerry/sedutil
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list