Re:The Catch 22 of Base64: Attacker Dilemma from a Defender ...
by jancsika on Tuesday May 01, 2018 @02:42PM
(#16970055)
Isn't this likely due to a second-order effect?
For example, there is (was?) a bug in nw.js with using @font-face to specify a font url that is in the same (local) location as the manifest. As a hack I tried specifying the font as a base64-encoded data url. It worked!
I had no use for base64, other than that there exists an interface for specifying data and it takes a base64-encoded string.
For example, there is (was?) a bug in nw.js with using @font-face to specify a font url that is in the same (local) location as the manifest. As a hack I tried specifying the font as a base64-encoded data url. It worked!
I had no use for base64, other than that there exists an interface for specifying data and it takes a base64-encoded string.