Skip to content

Commit b8bf920

Browse files
committed
Cleanup README.md
1 parent 0c8331a commit b8bf920

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -79,14 +79,15 @@ packages:
7979

8080
1. http-parser - ``http-parser-devel``
8181
2. systemd - ``systemd``
82-
3. jose - ``jose``, ``libjose-zlib-devel``, ``libjose-openssl-devel``
82+
3. jose >= 8 - ``jose``, ``libjose-devel``
83+
4. curl - curl (only needed for running tests)
8384

8485
### Building and Installing from Source
8586

8687
Building Tang is fairly straightforward:
8788

8889
$ autoreconf -if
89-
$ ./configure --prefix=/usr
90+
$ ./configure --prefix=/usr --libdir=/usr/lib64
9091
$ make
9192
$ sudo make install
9293

@@ -107,18 +108,19 @@ keys will be generated automatically.
107108
That's it! You're up and running!
108109

109110
### Key Rotation
111+
110112
It is important to periodically rotate your keys. This is a simple three step
111113
process. In this example, we will rotate only a signing key; but all key types
112114
should be rotated.
113115

114116
First, generate the new keys (see jose documentation for more options):
115117

116118
$ sudo jose jwk gen -i '{"alg":"ES512"}' -o /var/db/tang/newsig.jwk
117-
$ sudo jose jwk gen -i '{"alg":"ECDH"}' -o /var/db/tang/newexc.jwk
119+
$ sudo jose jwk gen -i '{"alg":"ECMR"}' -o /var/db/tang/newexc.jwk
118120

119121
Second, disable advertisement of the previous key:
120122

121-
# sudo mv /var/db/tang/oldsig.jwk /var/db/tang/.oldsig.jwk
123+
$ sudo mv /var/db/tang/oldsig.jwk /var/db/tang/.oldsig.jwk
122124

123125
Third, after some reasonable period of time you may delete the old keys. You
124126
should only delete the old keys when you are sure that no client require them

0 commit comments

Comments
 (0)