Promoted.
** Changed in: quassel (Ubuntu)
Status: In Progress => Fix Released
--
Quassel main inclusion report
https://bugs.launchpad.net/bugs/317892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
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.
--
Quassel main inclusion report
https://bugs.launchpad.net/bugs/317892
You received this bug notification because you are a member of Ubuntu
Bug
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 (Ubuntu)
Assignee
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 thou
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.
Ple
** Changed in: quassel (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => Kees Cook (kees)
Status: Incomplete => In Progress
--
Quassel main inclusion report
https://bugs.launchpad.net/bugs/317892
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Assigning to ubuntu-security as according to MIR kees is supposed to do
a code review (due to open port).
** Changed in: quassel (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
Status: New => Incomplete
--
Quassel main inclusion report
https://bugs.launchpad
