Package Details: sedutil 1.20.0-1

Git Clone URL: https://aur.archlinux.org/sedutil.git (read-only, click to copy)
Package Base: sedutil
Description: TCG OPAL 2.00 SED Management Program
Upstream URL: https://github.com/Drive-Trust-Alliance/sedutil
Licenses: GPL3
Submitter: R00KIE
Maintainer: R00KIE
Last Packager: R00KIE
Votes: 39
Popularity: 1.52
First Submitted: 2015-10-18 14:02 (UTC)
Last Updated: 2021-10-02 22:42 (UTC)

Dependencies (5)

Required by (0)

Sources (11)

Pinned Comments

R00KIE commented on 2016-08-27 21:39 (UTC)

To build this package you need to install one of the following: linux-headers: if you are using Arch's kernel linux-lts-headers: if you are using Arch's LTS kernel

Latest Comments

1 2 3 Next › Last »

pix3l commented on 2021-10-01 13:04 (UTC)

After changing version number to 1.20.0 it packaged and installed succesfully.

It's GPL, so why not move it to 'core', 'extra' or 'commmunity'? It should be included in ArchISO, so people using hardware encrypted drives, should be able to install ArchLinux on them. (it doesn't matter if SED drives are secure or not. Many folks want them and would like to utilize them. MAny alongside the LUKS as another security layer)

R00KIE commented on 2018-12-02 22:40 (UTC)

@ranran Just like you would add a normal entry, Something like:

efibootmgr -C -d /dev/sda -p 2 -L "Arch Linux" -l /vmlinuz-linux -u initrd=/initramfs-linux.img root=UUID="your_root_partition_uuid" rw quiet

ranran commented on 2018-11-26 21:41 (UTC)

Hi Rookie,

You said: "I forgot to mention before, there is a trick to creating the PBA entry when using efistub, the disk must be locked when you call efibootmgr, otherwise it will not know the uuid of the partition and obviously it will fail to start the PBA image using efistub. The trick here is to use a system on a usb drive to create the PBA uefi entry while the disk is locked. "

Can you please say how to use efistub/efibootmgr to add boot entry for mbr shadow ? I could not do it myself.

Thank you!!!!!!! ranran

Utini commented on 2018-10-31 08:26 (UTC)

Why on earth is this not in the official repos?!

R00KIE commented on 2017-05-21 18:58 (UTC)

Let's give it some time and see what happens. If the fork starts to get new code and stable releases then I suppose a change might be in order, until then lets wait and see.

darkbasic commented on 2017-05-21 17:27 (UTC)

Maybe it's time to change the git repo url? https://github.com/Drive-Trust-Alliance/sedutil/pull/56#issuecomment-302948612

mocambo commented on 2017-03-07 23:06 (UTC)

Unable to install on 32-bit system. Please fix. Error: can not find the makefile for configuration 'Release_i686' in project LinuxPBA See 'make help' for details. $ make help This makefile supports the following configurations: Debug Release Release_x86_64 Debug_x86_64

R00KIE commented on 2017-02-19 13:58 (UTC)

Works fine for me. You'll have to provide more context, otherwise with just that message it's not going to be easy to tell what the problem may be.

mh00h commented on 2017-02-19 00:14 (UTC)

This isn't installing with a DtaDevLinuxNvme.h error: linux/nvme.h no such file error

R00KIE commented on 2016-12-13 18:10 (UTC)

I forgot to mention before, there is a trick to creating the PBA entry when using efistub, the disk must be locked when you call efibootmgr, otherwise it will not know the uuid of the partition and obviously it will fail to start the PBA image using efistub. The trick here is to use a system on a usb drive to create the PBA uefi entry while the disk is locked. Regarding the bios changing the order of the entries or deleting entries, I believe that is bios/fw dependent, I don't have any problems with my laptop (Lenovo E560) but there are bug reports about that in the sedutil bug tracker, see [1-2]. [1] https://github.com/Drive-Trust-Alliance/sedutil/issues/66 [2] https://github.com/Drive-Trust-Alliance/sedutil/issues/27