Bug 1177180

Summary: please consider linking stoken against nettle
Product: [Fedora] Fedora Reporter: Nikos Mavrogiannopoulos <nmavrogi>
Component: stokenAssignee: Simone Caronni <negativo17>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: lnie, negativo17
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: stoken-0.81-2.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1374807 (view as bug list) Environment:
Last Closed: 2015-01-17 05:41:08 UTC Type: Bug
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: 1374807    

Description Nikos Mavrogiannopoulos 2014-12-24 21:25:35 UTC
Since version 0.8 stoken can be linked against nettle. Please consider linking against it, as there very few programs linking against libtomcrypt, and the main application that requires stoken already links against nettle (via gnutls).

Comment 1 Fedora Update System 2015-01-13 13:34:49 UTC
stoken-0.81-2.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/stoken-0.81-2.fc21

Comment 2 lnie 2015-01-14 06:42:46 UTC
stoken-0.81-2.fc21 works

Comment 3 Fedora Update System 2015-01-14 07:30:56 UTC
Package stoken-0.81-2.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing stoken-0.81-2.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-0648/stoken-0.81-2.fc21
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2015-01-17 05:41:08 UTC
stoken-0.81-2.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.