I’m curious if there is a preferred method for securing webfonts (@font-face) on a server. I’ve read a few bits about obfuscating the font file to prevent desktop use, and using .htaccess to block outside hot linking of the various files. Is there a more streamline approach to this method that anyone knows? Essentially I do not want users to have access for downloading the font files, etc.
That’s what I was summing, but what prevents someone from simply downloading the associated files within the web inspector? Most font hosting sites seem to have configured a secure method preventing access to files, or if access is permitted the font is unable to be used on the desktop because certain details are stripped out.
How would one serving their own fonts mimic these security measures? It seems quite difficult
@Rugg They’ve been working on them for quite some time which were released to a select few for beta testing. Mostly those who are “high profile” on the web. I hear they will be released pretty soon, though.
I’m not knowledgeable on base64 but basically I think it just encrypts the URL.