rpm/coolkey
SHA256
1
0
Fork 0
forked from pool/coolkey
Code Pull Requests Activity

Accepting request 512375 from home:jengelh:branches:security:chipcard

Browse Source 
- 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
This commit is contained in:
Stanislav Brabec 2017-07-26 18:49:37 +00:00 committed by Git OBS Bridge
parent 3042ae222b
commit 145e237c68
2 changed files with 9 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
coolkey.changes
View File

@ -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

16
coolkey.spec
View File

@ -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