zlacker

[parent] [thread] 5 comments
1. geor9e+(OP)[view] [source] 2024-06-23 18:23:22
>build Harfbuzz with -Dwasm=enabled and build wasm-micro-runtime, then add the resulting shared libraries, libharfbuzz.so.0.60811.0 and libiwasm.so to the LD_PRELOAD environment variable before running a Harfbuzz-based application such as gedit or GIMP

It'd be lovely if someone embedded the font in a website form to save us all the trouble of demoing it

replies(1): >>erk__+r
2. erk__+r[view] [source] 2024-06-23 18:27:36
>>geor9e+(OP)
It would not be of much use as no browser enables this experimental feature. So unless you somehow build a wasm build of Harfbuzz with the feature enabled and embed it on there nothing will happen.
replies(3): >>choppa+ba >>curtis+XN >>Lockal+ZN
◧◩
3. choppa+ba[view] [source] [discussion] 2024-06-23 19:47:14
>>erk__+r
And thank goodness it’s disabled, or we could have another JBIG2 https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-i...
replies(1): >>pennom+9r
◧◩◪
4. pennom+9r[view] [source] [discussion] 2024-06-23 22:24:28
>>choppa+ba
Yeah I know these posts are all funny use cases, but all I can see are font-based security nightmares.
◧◩
5. curtis+XN[view] [source] [discussion] 2024-06-24 03:51:50
>>erk__+r
Are there _any_ generally available consumer applications (document viewers, printers, obscure browsers, ...) that use a TTF font renderer with the WASM feature enabled?
◧◩
6. Lockal+ZN[view] [source] [discussion] 2024-06-24 03:53:29
>>erk__+r
According to demo, this feature has no opt-in, so if Android/iOS/any Linux distro ships with "better fonts feature for LibreOffice" it will be enabled in every text editor/browser/electron app, up to systemd blue screen of death.
[go to top]