Quassel main inclusion report

Bug #317892 reported by Jonathan Riddell
6
Affects Status Importance Assigned to Milestone
quassel (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Revision history for this message
Alexander Sack (asac) wrote :

Assigning to ubuntu-security as according to MIR kees is supposed to do a code review (due to open port).

Changed in quassel:
assignee: nobody → ubuntu-security
status: New → Incomplete
Changed in quassel:
assignee: ubuntu-security → kees
status: Incomplete → In Progress
Revision history for this message
Kees Cook (kees) wrote :

2009-01-27 15:55:06 Warning: SslServer: Certificate file /home/kees/.config/quassel-irc.org/quasselCert.pem does not exist
2009-01-27 15:55:06 Warning: SslServer: Unable to set certificate file
           Quassel Core will still work, but cannot provide SSL for client connections.
           Please see http://quassel-irc.org/faq/cert to learn how to enable SSL support.
2009-01-27 15:55:06 Warning: SslServer: Certificate file /home/kees/.config/quassel-irc.org/quasselCert.pem does not exist

Since quassel is SSL-aware, it should Depend on ca-certificates and use those by default.

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 317892] Re: Quassel main inclusion report

Note that only affects the split client packages which we do not expect to
put in main.

Currently when we install the server (core) package we create a cert (which
obviously doesn't have a CA associated with it).

The default upstream behavior is no SSL unless you manually make a cert.
We thought it was better to automatically provide SSL with no CA cert than
nothing.

I'm open to suggestions on how to deal with this?

Revision history for this message
Kees Cook (kees) wrote :

Beyond that, I don't see anything that really stands out to me. String handling is done via C++, auto-response elements look right, sprintf-like things are done sanely, and the SQL all looks to be injection-safe. +1 from me on a quick overview audit.

Changed in quassel:
assignee: kees → nobody
Revision history for this message
Scott Kitterman (kitterman) wrote :

Note: Kees and I discussed via IRC that the SSL cert question is only relevant for quassel-client and quassel-core which we plan to leave in Universe.

Revision history for this message
Martin Pitt (pitti) wrote :

Promoted.

Changed in quassel:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.