rpms/certmonger
7
0
Fork 0
Code Issues Pull Requests Releases Activity

- update to 0.38

Browse Source 
- catch cases where we can't read a PIN file, but we never have to log
    in to the token to access the private key (more of #688229)
This commit is contained in:
Nalin Dahyabhai 2011-03-24 15:30:29 -04:00
parent 2329f71493
commit 838b40e07a
3 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.gitignore vendored
View File

@ -15,3 +15,4 @@ certmonger-0.28.tar.gz
/certmonger-0.35.1.tar.gz /certmonger-0.35.1.tar.gz
/certmonger-0.36.tar.gz /certmonger-0.36.tar.gz
/certmonger-0.37.tar.gz /certmonger-0.37.tar.gz
/certmonger-0.38.tar.gz

7
certmonger.spec
View File

@ -1,5 +1,5 @@
Name: certmonger Name: certmonger
Version: 0.37 Version: 0.38
Release: 1%{?dist} Release: 1%{?dist}
Summary: Certificate status monitor and PKI enrollment client Summary: Certificate status monitor and PKI enrollment client
@ -109,6 +109,11 @@ exit 0
%{_localstatedir}/lib/certmonger %{_localstatedir}/lib/certmonger
%changelog %changelog
* Thu Mar 24 2011 Nalin Dahyabhai <nalin@redhat.com> 0.38-1
- update to 0.38
- catch cases where we can't read a PIN file, but we never have to log
in to the token to access the private key (more of #688229)
* Tue Mar 22 2011 Nalin Dahyabhai <nalin@redhat.com> 0.37-1 * Tue Mar 22 2011 Nalin Dahyabhai <nalin@redhat.com> 0.37-1
- update to 0.37 - update to 0.37
- be more careful about checking if we can read a PIN file successfully - be more careful about checking if we can read a PIN file successfully

2
sources
View File

@ -1 +1 @@
ff9650fb45352dfcb82bf601c36048fd certmonger-0.37.tar.gz ef66cd8f32e8188500854262a98a6a93 certmonger-0.38.tar.gz