nssbackup-team team mailing list archive

[Jean-Peer Lorenz <671785@xxxxxxxxxxxxxxxxxx>]

RFC1738 sec. 3.1 (http://tools.ietf.org/html/rfc1738.html): Within the user and password field, any ":",  "@", or "/" must be encoded.
This was not the case. Therefore, parsing such URIs failed. Now, any special characters contained in username or passphrase are encoded before parsing.

Please note: URIs are written in their encoded version into the
configuration file. If you want to set a username/password containing
special characters AND want to modify the configuration file directly,
you'll have to use an URI with encoded special characters. If you use
the configuration GUI, this is done for you automatically.

** Also affects: sbackup/0.11
   Importance: Undecided
       Status: New

** Also affects: sbackup/trunk
   Importance: Low
       Status: Confirmed

** Changed in: sbackup/0.11
       Status: New => Fix Committed

** Changed in: sbackup/0.11
   Importance: Undecided => Low

** Changed in: sbackup/0.11
     Assignee: (unassigned) => Jean-Peer Lorenz (peer.loz)

** Changed in: sbackup/trunk
     Assignee: (unassigned) => Jean-Peer Lorenz (peer.loz)

** Changed in: sbackup/trunk
       Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/671785

Title:
  Parsing remote URIs fails when username or password contains ':', '@' or '/'