I'd like to request unretire osslsigncode[1]. Originally it was retired because of being abandoned upstream, but now there is an actively maintained fork[2] with major release half a year ago and last commit less than 2 months ago. As I understand[3], original maintainer of Fedora osslsigncode package is not interested in maintaining it anymore. I can take it from there, but that would be my first package in Fedora (although I do maintain RPM packages elsewhere). I have already created scratch build of it at [4].

On Tue, Jun 4, 2019 at 8:16 AM Florian Weimer <fweimer(a)redhat.com&gt; wrote: > > * Marek Marczykowski-Górecki: > > > I'd like to request unretire osslsigncode[1]. Originally it was retired > > because of being abandoned upstream, but now there is an actively > > maintained fork[2] with major release half a year ago and last commit > > less than 2 months ago. As I understand[3], original maintainer of > > Fedora osslsigncode package is not interested in maintaining it anymore. > > I can take it from there, but that would be my first package in Fedora > > (although I do maintain RPM packages elsewhere). I have already created > > scratch build of it at [4]. > > How does it differ from pesign? Is it the Java support? > My understanding is that pesign does not do signatures for arbitrary containers, only PE binaries. I'm also uncertain if pesign does Authenticode style signing. I'm not sure if Secure Boot signatures are the same kind of signatures. osslsigncode is a reimplementation of Windows' signtool that can sign Windows installers, PE binaries, and CAB files for driver packages. It's required for shipping signed versions of Fedora Media Writer and the VirtIO drivers for Windows.