Bug 1419715

Summary:	Review Request: hwcrypto-native - enable digital signature for Chrome and Firefox > 52
Product:	[Fedora] Fedora	Reporter:	Mihkel Vain <mihkel.vain>
Component:	Package Review	Assignee:	Nobody's working on this, feel free to take it <nobody>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	lfarkas, package-review, plaes, quantum.analyst, rdieter
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-27 08:01:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	201449

Description Mihkel Vain 2017-02-06 20:38:49 UTC

Spec URL: https://mihkel.fedorapeople.org/SPECS/chrome-token-signing.spec
SRPM URL: https://mihkel.fedorapeople.org/SRPMS/chrome-token-signing-1.0.4-1.fc25.src.rpm

Description: This package enables users to give digital signature with Chrome, Firefox and possibly with other browsers too. Eventually this will obsolete firefox-esteid-plugin package:
https://apps.fedoraproject.org/packages/firefox-esteid-plugin

Firefox will drop old NPAPI plugins with version 52, so upstream created chrome-token-signing to fix that. Never mind that name, it has support for firefox too and they are actually planning to rename that repo.
https://github.com/open-eid/chrome-token-signing/issues/14

And I did not had any bright ideas either, so I left that name as it is provided by upstream. Of course I can rename it if someone has good ideas :)

Fedora Account System Username: mihkel
koji task: https://koji.fedoraproject.org/koji/taskinfo?taskID=17637848

Comment 1 Rex Dieter 2017-02-06 20:41:37 UTC

fyi, please do not use:

BuildRequires:	qt5-devel

that's a metapackage that pulls in a *lot* (kde-sig strongly encourages no official packages to use that).

what you have otherwise is probably sufficient:

BuildRequires:	pkgconfig(Qt5Core)
BuildRequires:	pkgconfig(Qt5Network)
BuildRequires:	pkgconfig(Qt5Widgets)

Comment 2 Mihkel Vain 2017-02-07 07:14:23 UTC

Good point. I removed qt5-devel from BuildRequires.

Spec URL: https://mihkel.fedorapeople.org/SPECS/chrome-token-signing.spec
SRPM URL: https://mihkel.fedorapeople.org/SRPMS/chrome-token-signing-1.0.4-2.el7.centos.src.rpm

koji task: https://koji.fedoraproject.org/koji/taskinfo?taskID=17644317

Comment 3 Mihkel Vain 2017-02-07 17:14:51 UTC

Just got an e-mail from upstream developer. They will plan to re-name that repo in following days. I will notify here what they decide and most likely use that name for fedora package as well.

Comment 4 Priit Laes 2017-03-04 12:16:06 UTC

They've moved to https://github.com/hwcrypto/hwcrypto-native

Info for packagers perspective: https://github.com/hwcrypto/hwcrypto-native/wiki/Installers

Comment 5 Mihkel Vain 2017-03-26 08:10:55 UTC

Re-built and re-organized spec file based on new sources from https://github.com/hwcrypto/hwcrypto-native

Spec URL: https://mihkel.fedorapeople.org/SPECS/hwcrypto-native.spec
SRPM URL: https://mihkel.fedorapeople.org/SRPMS/hwcrypto-native-17.3.14-1.fc25.src.rpm

Koji task: https://koji.fedoraproject.org/koji/taskinfo?taskID=18604538

Comment 6 Mihkel Vain 2017-03-28 05:56:23 UTC

New upstream release


Spec URL: https://mihkel.fedorapeople.org/SPECS/hwcrypto-native.spec
SRPM URL: https://mihkel.fedorapeople.org/SRPMS/hwcrypto-native-17.3.15-1.fc25.src.rpm

Koji task: https://koji.fedoraproject.org/koji/taskinfo?taskID=18641263

Comment 7 Levente Farkas 2017-08-23 22:28:21 UTC

any update with this package?

Comment 8 Elliott Sales de Andrade 2017-10-05 03:28:06 UTC

Upstream link https://github.com/hwcrypto/hwcrypto-native now redirects to https://github.com/web-eid/web-eid which has an empty master branch. The coverity_scan contains something of substance, but I don't really know what upstream is doing.

Comment 9 Elliott Sales de Andrade 2019-03-27 08:01:11 UTC

I'll close this as upstream (at least as linked here) appears to be dead.