uvf exception request konversation 0.19 --> 1.0

Bug #58270 reported by Brandon Holtsclaw
6
Affects Status Importance Assigned to Milestone
konversation (Ubuntu)
Fix Released
Undecided
Brandon Holtsclaw

Bug Description

builds fine and has been tested in my private repos for many weeks, fixes nearly every malone bug thats open.

Revision history for this message
Brandon Holtsclaw (imbrandon) wrote :

changelog attachment

Changed in konversation:
assignee: nobody → imbrandon
status: Unconfirmed → Confirmed
Revision history for this message
Jonathan Riddell (jr) wrote :

I support this request, the konversation developers have deliberately timed their release to be scheduled with Kubuntu.

Revision history for this message
Colin Watson (cjwatson) wrote :

The only thing I noticed that might need additional checking is:

* DCC file transfers now support file names containing spaces on send, receive
  and resume. The automatic replacement of spaces with underscores in file names
  can now be optionally disabled in the DCC preferences.

Could somebody make sure that Konversation will never try to spawn commands via the shell (including the system() libc function) that operate on DCC-received files, at least not without escaping any characters not in a known-good set to avoid shell metacharacter expansion?

Otherwise, this looks good, thanks.

Revision history for this message
Hein (sho) wrote :

Hi, Konversation's maintainer and release manager here.

We interact with files to be sent or received via DCC via standard KDE/Qt library functions and KDE KIO, not ever by manually running commands on a shell.

Also, note that the above feature is disabled by default.

Changed in konversation:
status: Confirmed → 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.