Elointz
Elointz
Just out of curiosity, could this have been CloudBleed?
Totally agree. While there _may_ not be any known vulnerabilities for now, I agree it should at least be classified as "low" (Retire.js doesn't have "informational").
For our implementation it would very much be needed as described above with combination of a custom file. Now when providing a custom file it overrides the provided databases.
That sounds like a plan, but it's not very high prio. Currently we call `retire` twice, once with the provided database and then with our custom json-file.
@eoftedal I see you are working on [email protected], can you include this one too? The parameter wasn't being used so just drop it for now.
Great! Yes, that would solve the initial problem that dropExternal was supposed to do.