verify_message_rfc7518 + sign_message_rfc7518 do update - related to #45
Karel Miko
5 years ago
| 827 | 827 | Same as L<sign_message|/sign_message> only the signature format is as defined by L<https://tools.ietf.org/html/rfc7518> |
| 828 | 828 | (JWA - JSON Web Algorithms). |
| 829 | 829 | |
| 830 | B<BEWARE:> This creates signatures according to the structure that RFC 7518 describes but does not apply | |
| 831 | the RFC logic for the hashing algorithm selection. You'll still need to specify, e.g., SHA256 for a P-256 key | |
| 832 | to get a fully RFC-7518-compliant signature. | |
| 833 | ||
| 830 | 834 | =head2 verify_message |
| 831 | 835 | |
| 832 | 836 | my $pk = Crypt::PK::ECC->new($pub_key_filename); |
| 842 | 846 | |
| 843 | 847 | Same as L<verify_message|/verify_message> only the signature format is as defined by L<https://tools.ietf.org/html/rfc7518> |
| 844 | 848 | (JWA - JSON Web Algorithms). |
| 849 | ||
| 850 | B<BEWARE:> This verifies signatures according to the structure that RFC 7518 describes but does not apply | |
| 851 | the RFC logic for the hashing algorithm selection. You'll still need to specify, e.g., SHA256 for a P-256 key | |
| 852 | to get a fully RFC-7518-compliant signature. | |
| 845 | 853 | |
| 846 | 854 | =head2 sign_hash |
| 847 | 855 | |