Bug 219408

Summary: [NEW PORT] security/sedutil Self Encrypting Drive utility
Product: Ports & Packages Reporter: Kenneth D. Merry <ken>
Component: Individual Port(s)Assignee: freebsd-ports-bugs mailing list <ports-bugs>
Status: New ---    
Severity: Affects Only Me CC: asomers, brd, emaste
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
Description Flags
sedutil port shar archive
Updated sedutil port none

Description Kenneth D. Merry freebsd_committer 2017-05-19 20:47:39 UTC
Created attachment 182746 [details]
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:


Alexander Motin's FreeBSD changes:


Alexander's and my changes combined:

Comment 1 Kenneth D. Merry freebsd_committer 2017-05-23 19:33:54 UTC
Created attachment 182836 [details]
Updated sedutil port

I changed the version to 1.12.  Thanks for the feedback!
Comment 2 Ed Maste freebsd_committer 2019-06-09 10:44:10 UTC
It looks like upstream is willing to merge the changes but is looking for a contributor agreement?

Comment 3 Rene Ladan freebsd_committer 2019-11-05 21:03:32 UTC
Ports commit bit safekept.