security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

reformat Vanadium default connections

Browse Source
This commit is contained in:
Daniel Micay 2023-05-06 15:33:02 -04:00
parent c723563ba6
commit fcbce2d409
1 changed files with 16 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
static/faq.html
View File

@ -816,6 +816,12 @@
certain apps bundled with the OS and other apps available in our
repository.</p>
</li>
<li>
<p>Vanadium, our browser and WebView implementation, uses
<code>update.vanadium.app</code> to check for updates to components
providing revoked certificates and other data. It downloads the
components from <code>dl.vanadium.app</code>.</p>
</li>
<li>
<p>An HTTPS connection is made to
https://time.grapheneos.org/generate_204 to update the time with a
@ -1018,21 +1024,19 @@
</li>
</ul>
<p>Other Vanadium browser connections are initiated by the user such as the
search engine (defaults to DuckDuckGo), websites and retrieving favicons for
your bookmarks and the frequent sites shown on the home page. We enable
connection and cache partitioning to keep connections separate between
different sites. There are a few parts of state partitioning still being
implemented including cookie partitioning which is currently in the testing
phase but causes too many compatibility issues to fully deploy it by default
without any exceptions like Brave's heuristics to disable it for cross-site
login flows, etc.</p>
<p>Unlike Chrome/Chromium, Vanadium WebView does not make connections beyond
those initiated by the app using it so there are no default connections from
apps using the WebView.</p>
<p>Vanadium browser uses <code>update.vanadium.app</code> to check for updates
to components providing revoked certificates and other data. It downloads the
components from <code>dl.vanadium.app</code>. Other connections are initiated
by the user such as the search engine (defaults to DuckDuckGo), websites and
retrieving favicons for your bookmarks and the frequent sites shown on the
home page. We enable connection and cache partitioning to keep connections
separate between different sites. There are a few parts of state partitioning
still being implemented including cookie partitioning which is currently in
the testing phase but causes too many compatibility issues to fully deploy it
by default without any exceptions like Brave's heuristics to disable it for
cross-site login flows, etc.</p>
</article>
<article id="other-connections">