From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] Galene security review
Date: Tue, 10 Jun 2025 22:33:43 +0200 [thread overview]
Message-ID: <875xh3nxp4.wl-jch@irif.fr> (raw)
Hi,
Back in January, Galene underwent a security review by Sven Vink of
Radically Open Security, funded by NLnet. It was very interesting, we had
some very interesting chats with the reviewer, and I learned a lot.
The document is here:
https://galene.org/NGICore%20Galene%20penetration%20test%20report%202025%201.0.pdf
The summary is on page 5:
> During this crystal-box penetration test we found 7 Moderate and
> 5 Low-severity issues.
The bad news are the path traversal issues; as a mitigating factor,
they're only exposed to privileged users (you need to have the "record"
permissions). They have been fixed in Galene back in January.
Most issues found by the review were fixed in Galene 0.96.2. Exceptions:
* password policy: Galene accepts weak passwords by design: I find it
convenient to organise meetings with a password that can easily be
dictated on the phone, especially when the meetings are not confidential;
* HSTS (security headers): this complicates administration, and is
therefore at odds with the goals of Galene;
* protection against brute force attacks and disk space exhaustion;
* insufficient logging.
Thanks to Sven Vink for his work and the interesting chats, and to NLnet
for funding the review.
-- Juliusz
reply other threads:[~2025-06-10 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xh3nxp4.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox