diff options
| author | Josh Stone <jistone@redhat.com> | 2009-06-10 17:32:28 -0700 |
|---|---|---|
| committer | Josh Stone <jistone@redhat.com> | 2009-06-10 17:32:28 -0700 |
| commit | 87c589a9c86356f91cab1501304eff0c302a052c (patch) | |
| tree | 86dbef50260bdfdf8a7928a0a3261836896f9a47 | |
| parent | e0d0671766ed452a1eb141ef1c6e0ad19149c88a (diff) | |
| download | systemtap-steved-87c589a9c86356f91cab1501304eff0c302a052c.tar.gz systemtap-steved-87c589a9c86356f91cab1501304eff0c302a052c.tar.xz systemtap-steved-87c589a9c86356f91cab1501304eff0c302a052c.zip | |
Reformat the module signing NEWS
| -rw-r--r-- | NEWS | 15 |
1 files changed, 8 insertions, 7 deletions
@@ -1,12 +1,13 @@ * What's new -- Module signing: If the appropriate nss libraries are available on your system, - stap will sign each compiled module using a self-generated certificate. - This is the first step toward extending authority to load certain modules to - unprivileged users. For now, if the system administrator adds a certificate - to a database of trusted signers (stap-authorize-signing-cert), modules signed - using that certificate will be verified by staprun against tampering. - Otherwise, you should notice no difference in the operation of stap or staprun. +- Module signing: If the appropriate nss libraries are available on your + system, stap will sign each compiled module using a self-generated + certificate. This is the first step toward extending authority to + load certain modules to unprivileged users. For now, if the system + administrator adds a certificate to a database of trusted signers + (stap-authorize-signing-cert), modules signed using that certificate + will be verified by staprun against tampering. Otherwise, you should + notice no difference in the operation of stap or staprun. * What's new in version 0.9.7 |