Create Security documentation

[ssspacez]

I didn’t find much information about how security works with snaps. Just this on a quick look:

Documentation:

is confined from the OS and other apps through security mechanisms, but can exchange content and functions with other snaps according to fine-grained policies controlled by the user and the OS defaults.

Store:

Not only are snaps kept separate, their data is kept separate too. Snaps communicate with each other only in ways that you approve.

There’s a lot of misinformation going on recently and I think the lack of a Security section on the documentation, or the store, or even the main page is not helping.

Suggestion: Create a Security section and explain how everything works, please be transparent and don’t use a lot of technical terms, this is aimed at users.

Snap documentation | Snapcraft documentation

[ogra]

There are:

Security policies

Without custom flags at installation, or subsequent interface connections, snaps are confined to a restrictive security sandbox with no access to system resources outside of the snap. Snap developers need to be aware of the scope their applications have from within the snap. Security policies and store policies work together to allow developers to quickly update their applications, and to provide safety to end users, and this document describes the sandbox and how to configure and work with th…

And the core security whitepaper:

https://developer.ubuntu.com/core/documentation

[ssspacez]

Almost no one will check these links above, I’m talking about creating a Security section here:

Snap documentation | Snapcraft documentation

[ssspacez]

It doesn’t need be too long or have multiple items, one page explaining will probably be enough for most people.

The technical details could be elsewhere, just put a link like: “Learn more about Security”, and developers and high skilled users could access if they want to.

[ogra]

then you should probably report it at

Experimental documentation site

Hello all, For about a year now we have been experimenting with using this forum as a mechanism to maintain the documentation for the project. This has been working quite well in several fronts: Increased visibility for the content Content trivially editable by everyone Forum’s spam control helps preventing abuse Searches hit the documentation too Documentation can be easily discussed Nice change tracking That said, there are some downsides too: Lack of a consolidated picture Documentation…