@@ -6,7 +6,7 @@ JSON Web Signature (JWS)
6
6
JSON Web Signature (JWS) represents content secured with digital signatures
7
7
or Message Authentication Codes (MACs) using JSON-based data structures.
8
8
9
- It's assumed that you know all you need to know about key handling if not
9
+ It is assumed that you know all you need to know about key handling if not
10
10
please spend some time reading keyhandling _ .
11
11
12
12
When it comes to JWS there are basically 2 things you want to be able to do: sign some data and verify that a
@@ -27,9 +27,9 @@ There are few steps you have to go through. Let us start with an example and the
27
27
28
28
The steps:
29
29
30
- 1. You need keys, one of more. If you provide more then one the software will pick one that has all the necessary
31
- qualifications. The keys *MUST * be instances of :py:class: `cryptojwt.jwk.JWK ` or of sub classes of that class.
32
- 2. You need the information that are to be signed. It must be in the form of a string.
30
+ 1. You need keys, one or more. If you provide more than one the software will pick one that has all the necessary
31
+ qualifications. The keys *MUST * be an instance of :py:class: `cryptojwt.jwk.JWK ` or of a sub class of that class.
32
+ 2. You need the information that is to be signed. It must be in the form of a string.
33
33
3. You initiate the signer, providing it with the message and other needed information.
34
34
4. You sign using the compact or the JSON method as described in section 7 of RFC7515 _ .
35
35
@@ -50,10 +50,10 @@ Verifying a signature works like this (_jws comes from the first signing example
50
50
51
51
The steps:
52
52
53
- 1. As with signing, you need a set of keys that can be used to verify the signature. If you provider more then
54
- one possible, then the default is to use then one by one until one works or the list is empty.
53
+ 1. As with signing, you need a set of keys that can be used to verify the signature. If you provide more than
54
+ one key, the default is to use them one by one until one works or the list is empty.
55
55
2. Initiate the verifier. If you have a reason to expect that a particular signing algorithm is to be used you
56
- should give that information to the verifier as shown here. If you don't know you can leave it out.
56
+ should give that information to the verifier as shown here. If you don't know, you can leave it out.
57
57
3. Verify, using the compact or JSON method.
58
58
59
59
Or slightly different::
@@ -89,4 +89,4 @@ If you have Key Jar instead of a simple set of keys you can do (not showing how
89
89
This is a trick that is used in :py:class: `cryptojwt.jwt.JWT `
90
90
91
91
92
- .. _RFC7515 : https://tools.ietf.org/html/rfc7515
92
+ .. _RFC7515 : https://tools.ietf.org/html/rfc7515
0 commit comments