Package Details: sedutil 1.49.7-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
Keywords: tcg
Licenses: GPL3
Submitter: R00KIE
Maintainer: 2bluesc (ozz)
Last Packager: 2bluesc
Votes: 45
Popularity: 0.075303
First Submitted: 2015-10-18 14:02 (UTC)
Last Updated: 2025-03-02 19:58 (UTC)

Dependencies (8)

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

« First ‹ Previous 1 2 3 4 5

tarm commented on 2016-01-27 08:35 (UTC)

Hey you answered to my request over on SEdutils github page for wanting yubikey support and explained how your custom scripted pba works. I have compiled the package. But I am not clear on exactly what its going to install? Is it simply the custom pba image and sedutil program? The reason I ask is in my specific situation I have to actually flash the pba image from a rescue/bootable flash drive. I can not run the sedutil program from inside the os. Now I have a rescue disk I created from the msed program. I made a few changes so I could add all the pba images. This basically gives me a standalone install utility tool so I can push whatever pba I want directly from the syslinux recovery flash drive. I understand I need to install the yubikey personalaztion tool package to setup the yubikey for C&R etc of course. But I am not entirely clear on what I have to do to setup the luks locked file with the PWD I am sealing in it? Since I am having to do it from a syslinux busybox setup am I needing to do it from that syslinux setup? Again thanks for any help you may be able to give me.

R00KIE commented on 2015-12-30 15:41 (UTC)

@crepererum You are correct. I don't have a UEFI machine to test so I'm not going to claim to support something I can't test properly. It shouldn't be too hard to adapt the mklinuxpba-bios script for uefi, but like I said it needs proper testing. From what I've been told some (older) firmwares are a bit picky about the uefi partition, there is also the matter of secure boot that I would need to try for myself, at least so that instructions can be put on a wiki page of how to make things work. You can find bios and uefi images here [1] but I suppose they support only password input and the keyboard layout is set to US. [1] https://github.com/Drive-Trust-Alliance/exec

crepererum commented on 2015-12-30 14:58 (UTC)

Am I right assuming that this only works for a BIOS-driven boot and not for UEFI boot procedures?

« First ‹ Previous 1 2 3 4 5