This site has been retired. For up to date information, see handbook.gnome.org or gitlab.gnome.org.


[Home] [TitleIndex] [WordIndex

Ideas for the privacy campaign

The GNOME Foundation ran a campaign to raise funds to implement privacy features within GNOME. Some of those features will need to be implemented by professional contractors, upstream developers on a number of projects, community members, or the participants in one of our integration programmes.

On 14 August 2016, a session was held on this topic at GUADEC.

application containment

enhanced disk encryption support

Tor integration

Privacy Policies

user control over diagnostic reporting features

robust VPN routing

application integration with system-wide privacy settings

controls for how GNOME devices are identified on local networks

Web, the GNOME browser

All these suggestions are obsolete. Our GLib and libsoup security issues are more important than anything we can change in Epiphany. -- (MichaelCatanzaro, August 2016)

OTR support for Empathy/Telepathy

improve GPG user experience

GNOME Keysign

(proposed by TobiasMueller)

A successful Summer of Code project made an OpenPGP Keysigning tool happen. Code is currently hosted at https://github.com/muelli/geysigning for now, but should change once a few releases were made, so expect that link to become defunct. The project's wiki page is GnomeKeysign.

Signing another person's key is one of the first steps when trying to communicate securely (after generating a key, see proposal above). For now, signing someone's keys and following best practices is tedious and error-prone. The tool helps to make that a much more pleasant experience.

Good enhancements to the existing implementation would be:

* Michael thinks we won't want to have this installed by default, so the benefit will be quite limited. Would prefer to merge these features into an existing application (Geary? seahorse?) (-- MichaelCatanzaro, August 2016)

Good crypto UX

Make crypto usable by non-technical users:

  1. Nice UI or make it completely transparent wherever it's applied (OTR, Evolution, cloud services, ...)
  2. No scary technical messages.
  3. Should just work or be as easy as possible (for example looking at the OTR support of Pidgin for example which is quite annoying - telepathy/empathy should do better.)

GNOME Bitcoin Wallet

Disable USB on lockscreen

(proposed by TobiasMueller)

USB offers a large attack surface. We could reduce the risk of malicious USB devices by telling Linux to not accept new USB devices if the screen is locked. A reference is here: http://seclists.org/oss-sec/2014/q3/329

Protect users from rogue USB drives

(proposed by MichaelCatanzaro)

Along the lines of the proposal above: nowadays a malicious USB storage device will identify itself as a keyboard or network device or a USB hub to the operating system. I wonder if it would be feasible to protect users against this, e.g. by popping up a dialog with a big picture of a storage drive opposite an image of the other device and asking "What did you plug in?" E.g. see https://hakshop.myshopify.com/collections/usb-rubber-ducky/products/usb-rubber-ducky-deluxe for a readily-available Flash drive that identifies as a keyboard.

fix core libraries

(proposed by TobiasMueller)

Currently, we have known issues in several libraries which I consider to be "core" of GNOME and the wider ecosystem, which are very likely security relevant (think integer or buffer overflows in poppler or librsvg). Interest in maintaining these libraries or fixing those specific issues seems to have waned and the problems to solve are not easy. I can share details on request. We could attempt to bring people knowledgeable in these libraries and security people together to get some problems fixed.

Harden Tracker to prevent it from leaking any data

See https://bugzilla.gnome.org/show_bug.cgi?id=735406

Factory reset

Add a factory reset option to the control center, which would allow users to delete all data, apps and settings, and restore the machine to its original state.

This is useful for protecting your privacy when passing a computer you have used on to another person or organisation.

Secure application password storage

(proposed by AllanDay)

As described by Stef, during his 2013 GUADEC Lecture (from slide 37):

http://www.superlectures.com/guadec2013/more-secure-with-less-security

Last login notification

(proposed by AllanDay)

Add an option to show the time of the last login in a notification when the user logs in/unlocks.

Presentation mode

(proposed by AllanDay)

This feature would allow displays that are being used for presentations (such as projectors) to be specified by the user. These presentation displays would then be treated differently:

This feature will avoid the many privacy issues associated with giving presentations (particularly if those presentations are being streamed live). Personal wallpapers (such as those showing your kids) wouldn't be displayed publicly, and you wouldn't risk leaking personal information to the room, such as when typing into the URL bar in your browser.

Guest windows in Web

(proposed by AllanDay)

It is quite common for someone to ask to use your web browser for a second, either to check their mail or check a website. This can be an inadvertent threat to your privacy - entering an URL displays parts of your browsing history. Guest windows would solve this - these windows would not use your stored history, passwords, bookmarks or other data.

seahorse update/redesign

GLib TLS security

libsoup HTTPS security

Port GRegex to PCRE2

(proposed by SébastienWilmet)

PCRE is deprecated in favour of a new API called PCRE2. The old PCRE will only receive sporadic bugfix releases for some time.

755693 - future of GRegex (solution B). Exposing the JIT functionality is a plus.

Interested and available developer for the task: SébastienWilmet

More static analysis tools for C/GObject

(proposed by SébastienWilmet)

Develop more static analysis tools for C/GObject, for example in Tartan.

Example: check that GObject signal callbacks have a good prototype.

Interested and available developer for the task: SébastienWilmet


2024-10-23 11:07