fix: backport regex change from 8.0.1#20
Conversation
|
This would be nice to get backported to version 7 of For example, And I'm sure there's more packages like this. |
|
We are facing the same issue with |
|
Friendly ping, @nlf You released the previous updates for ssri. Could you look at this backport? |
|
I need write access |
|
I'm just learning this platform so I'll look for other instances of this software on my local directories--is that part of the pipeline so to say? Thanks. |
|
@nlf @darcyclarke @wraithgar @isaacs would it be possible to get this merged and released? We've coming up to this being open for a month now with the community being very vocal on this being annoying and showing a clear desire for the patch, which was promptly landed for the v6 & v8 lines in a desire to make it easy for devs to update which this version would also do. If there is anything I can do on my end to help speed up getting this landed please let me know, but so far I've not had any review from the npm team :( |
|
Am I holding up this project |
| const STRICT_SRI_REGEX = /^([^-]+)-([A-Za-z0-9+/=]{44,88})(\?[\x21-\x7E]*)?$/ | ||
| const VCHAR_REGEX = /^[\x21-\x7E]+$/ | ||
|
|
||
| const SsriOpts = figgyPudding({ |
There was a problem hiding this comment.
Approve remove const SsriOpts = figgyPudding({
| const STRICT_SRI_REGEX = /^([^-]+)-([A-Za-z0-9+/=]{44,88})(\?[\x21-\x7E]*)?$/ | ||
| const VCHAR_REGEX = /^[\x21-\x7E]+$/ | ||
|
|
||
| const SsriOpts = figgyPudding({ |
There was a problem hiding this comment.
Approve remove const SsriOpts = figgyPudding({
|
|
||
| const BASE64_REGEX = /^[a-z0-9+/]+(?:=?=?)$/i | ||
| const SRI_REGEX = /^([^-]+)-([^?]+)([?\S*]*)$/ | ||
| const STRICT_SRI_REGEX = /^([^-]+)-([A-Za-z0-9+/=]{44,88})(\?[\x21-\x7E]*)*$/ |
nlf
left a comment
There was a problem hiding this comment.
thank you for doing this work! sorry for the delay, but i'm about to publish it right now
|
this was merged via commit 809c84d and published as ssri@7.1.1 |
|
@nlf I'd say no problem but... it was a long wait 😅 Are you able to fast-track getting the npm advisory updated to include |
Backport of #17 so it's easier for people to patch.
Once/if this is merged and released, the advisory will need to be updated to reflect the new vulnerability/fixed range to allow > 7.0.2
Relates to #19.
References