From 145e237c68e3959ca53fd42d550815c5105fb2c3eb402d51df22365bbb6c98c8 Mon Sep 17 00:00:00 2001 From: Stanislav Brabec Date: Wed, 26 Jul 2017 18:49:37 +0000 Subject: [PATCH] Accepting request 512375 from home:jengelh:branches:security:chipcard - Remove vision statement and development methods from description. OBS-URL: https://build.opensuse.org/request/show/512375 OBS-URL: https://build.opensuse.org/package/show/security:chipcard/coolkey?expand=0&rev=19 --- coolkey.changes | 5 +++++ coolkey.spec | 16 ++++------------ 2 files changed, 9 insertions(+), 12 deletions(-) diff --git a/coolkey.changes b/coolkey.changes index 28d0e7b..1ddf270 100644 --- a/coolkey.changes +++ b/coolkey.changes @@ -1,3 +1,8 @@ +------------------------------------------------------------------- +Mon Jul 24 23:02:16 UTC 2017 - jengelh@inai.de + +- Remove vision statement and development methods from description. + ------------------------------------------------------------------- Fri Jul 21 14:00:08 CEST 2017 - sbrabec@suse.com diff --git a/coolkey.spec b/coolkey.spec index 15950f7..b40415c 100644 --- a/coolkey.spec +++ b/coolkey.spec @@ -79,12 +79,8 @@ keys are automatically provisioned with certificates, keys, and a PIN, unique for that user by the Red Hat Certificate System. Once the CoolKey is provisioned, the user can take the key to any system and use it to login (authenticate), send and receive signed and encrypted -email, or participate in secure messaging or IRC communication. Using a -CoolKey should be as easy as starting a car. To accomplish that vision, -we are focusing on building complete support for CoolKey on exactly one -token. As the system is built out, we can add token support. CoolKeys -are based on JavaCard 1.2. We are testing with Axalto Egate Cyberflex -cards, which are available in both smart card and USB Fob form factors. +email, or participate in secure messaging or IRC communication. +CoolKeys are based on JavaCard 1.2. %package devel Summary: CoolKey and CAC PKCS #11 PKI Module for Smart Cards @@ -103,13 +99,9 @@ keys, and a PIN unique to that user by the Red Hat Certificate System. Once the CoolKey is provisioned, the user can take the key to any system and use it to login (authenticate), send and receive signed and encrypted email, or participate in secure messaging or IRC -communication. Using a CoolKey should be as easy as starting a car. +communication. -To accomplish that vision we are focusing on building complete support -for CoolKey on exactly one token. As the system is built out, we can -add token support. CoolKeys are based on JavaCard 1.2. We are testing -with Axalto Egate Cyberflex cards, which are available in both smart -card and USB Fob form factors. +CoolKeys are based on JavaCard 1.2. %prep %setup -q