Re:LibreOffice running natively in the browser via WebAssembly
by iggldiggl on Wednesday February 16, 2022 @04:59AM
(#30358092)
> Preventing a process from deciding itself which files to access disables so many attack vectors.
It also disables a lot of existing use cases and file types (basically any multi-file file format):
Multi-part archives, multi-part video files, playlists, videos with separate subtitle files, HTML documents containing links to other local HTML documents or referencing various sub-resources (images/videos/audio/style sheets/scripts/...), Audacity projects, images with metadata in external sidecar files, ditto for georeferenced images, QGIS projects, AutoCAD's lock file implementation, DWG files as such, …
Edit: And since we're talking about Office software: Spreadsheets referencing data from other spreadsheets stored in separate files…
Re:LibreOffice running natively in the browser via WebAssembly
by thorstenb on Wednesday February 16, 2022 @05:13AM
(#30358199)
With LibreOffice, the nice thing is you can chose. if you want all of the above - install the native version.
Re:LibreOffice running natively in the browser via WebAssembly
by iggldiggl on Wednesday February 16, 2022 @05:32AM
(#30358322)
In this particular instance yes, of course – this was more with reference to the dreams of some people who want everything to work like that.
Re:LibreOffice running natively in the browser via WebAssembly
by vitiral on Wednesday February 16, 2022 @08:35AM
(#30359708)
It would work differently. Libre office would think it was accessing a local file, but really it would be whatever the JavaScript tells it exists. So you might be able to implement a rudimentary online doc and storage system using this if your users could suffer tab sizes of 300MiB for every open doc.
Re:LibreOffice running natively in the browser via WebAssembly
by master-lincoln on Wednesday February 16, 2022 @04:45AM
(#30358014)
Sounds like the upcoming File Access API is exactly what you have in mind
https://developer.mozilla.org/en-US/docs/Web/API/File_System...
What is likely to be seen as a bug by others, is actually the thing that gives me hope. There's no way for a WebAssembly program to access the host file system. I hope it stays that way.
If the Wasm host can, in a foolproof and easy to verify way, offer the user dialog boxes to read/write single files... we'd have the "PowerBox" that is required to make a modern capability based operating system.
Preventing a process from deciding itself which files to access disables so many attack vectors.