The browser cannot protect the font source. Once the information is received by the browser, you can safely assume that the user will have full access to the fact that you send it.
Thus, the problem of preserving protected fonts is carried out either at the legal level (by selecting fonts that allow embedding) or through obfuscation schemes on the server side. For example, look at the fonts embedded in TypeKit:
@font-face { font-family:"rosewood-std-fill-1"; src:url(data:font/opentype;base64,d09GRgABAAAAAEa4ABMAAAAA2XwA.....); font-style:normal; font-weight:400; }
The font is obfuscated through the base64 encoding process. In addition, the font is divided into two parts, and the number of glyphs is limited only by those that the website needs.
On the other hand, looking at the FontSquirrel and Google Font API @font-face kits, you can see that the actual font source is sent to the user - no obfuscation is required. In addition, font owners may require some form of attribution, such as
If the font is a free font ($ 0.00 license fee), you can use this font to attach Font-Face, but only if you placed a link to www.exljbris.nl on your page and / or put this notification
in your CSS file as close as possible to the code fragment that the Font-Face font insert of that font declares.
seen in this license . Therefore, from all this we can safely conclude that the problem of protecting fonts does not occur on the client side, but rather falls on the shoulder of the developer, and therefore browsers can not and do nothing to stop users from accessing these fonts.
Yi jiang
source share