mirror of https://github.com/mastodon/mastodon
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
b241f20bd2
* Add support for latest HTTP Signatures spec draft https://www.ietf.org/id/draft-ietf-httpbis-message-signatures-00.html - add support for the “hs2019” signature algorithm (assumed to be equivalent to RSA-SHA256, since we do not have a mechanism to specify the algorithm within the key metadata yet) - add support for (created) and (expires) pseudo-headers and related signature parameters, when using the hs2019 signature algorithm - adjust default “headers” parameter while being backwards-compatible with previous implementation - change the acceptable time window logic from 12 hours surrounding the “date” header to accepting signatures created up to 1 hour in the future and expiring up to 1 hour in the past (but only allowing expiration dates up to 12 hours after the creation date) This doesn't conform with the current draft, as it doesn't permit accounting for clock skew. This, however, should be addressed in a next version of the draft: https://github.com/httpwg/http-extensions/pull/1235 * Add additional signature requirements * Rewrite signature params parsing using Parslet * Make apparent which signature algorithm Mastodon on verification failure Mastodon uses RSASSA-PKCS1-v1_5, which is not recommended for new applications, and new implementers may thus unknowingly use RSASSA-PSS. * Add workaround for PeerTube's invalid signature header The previous parser allowed incorrect Signature headers, such as those produced by old versions of the `http-signature` node.js package, and seemingly used by PeerTube. This commit adds a workaround for that. * Fix `signature_key_id` raising an exception Previously, parsing failures would result in `signature_key_id` being nil, but the parser changes made that result in an exception. This commit changes the `signature_key_id` method to return `nil` in case of parsing failures. * Move extra HTTP signature helper methods to private methods * Relax (request-target) requirement to (request-target) || digest This lets requests from Plume work without lowering security significantly. |
5 years ago | |
|---|---|---|
| .. | ||
| account_controller_concern.rb | 6 years ago | |
| account_owned_concern.rb | 6 years ago | |
| accountable_concern.rb | 7 years ago | |
| authorization.rb | 7 years ago | |
| cache_concern.rb | 6 years ago | |
| challengable_concern.rb | 6 years ago | |
| export_controller_concern.rb | 6 years ago | |
| localized.rb | 5 years ago | |
| rate_limit_headers.rb | 5 years ago | |
| session_tracking_concern.rb | 7 years ago | |
| sign_in_token_authentication_concern.rb | 5 years ago | |
| signature_authentication.rb | 7 years ago | |
| signature_verification.rb | 5 years ago | |
| status_controller_concern.rb | 6 years ago | |
| two_factor_authentication_concern.rb | 5 years ago | |
| user_tracking_concern.rb | 7 years ago | |