Hi Chris! I cannot comment on the libunity-webapps's usage of SQLite -- I'll leave that to the webapps developers.
However, our Online Accounts extension is probably also causing the system libsqlite to be loaded into FF process space: we are opening (via js-ctypes) a library called libwebaccounts.so, which in turn depends on libaccounts-glib, which uses libsqlite. Is this unsafe as well?
I don't think that FF code would have access to the system libsqlite symbols in this case.
Hi Chris! I cannot comment on the libunity-webapps's usage of SQLite -- I'll leave that to the webapps developers.
However, our Online Accounts extension is probably also causing the system libsqlite to be loaded into FF process space: we are opening (via js-ctypes) a library called libwebaccounts.so, which in turn depends on libaccounts-glib, which uses libsqlite. Is this unsafe as well?
I don't think that FF code would have access to the system libsqlite symbols in this case.