Parsing remote URIs fails when username or password contains ':', '@','/' or '?'
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
sbackup | Status tracked in Trunk | |||||
0.11 |
Fix Released
|
Low
|
Jean-Peer Lorenz | |||
Trunk |
Fix Released
|
Low
|
Jean-Peer Lorenz | |||
sbackup (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Dist: Ubuntu 10.10
SBackup version: 0.11.3
Installed from: apt
When setting up a remote target as backup destination the program crashes if a / is used in the password field.
Steps to reproduce:
1) Open Simple Backup-
2) Destination -> Use a remote site -> Connect...
3) Enter a / character in the password field (or any password containing one)
4) Connect
Stacktrace:
Traceback (most recent call last):
File "/usr/share/
self.
File "/usr/share/
if splituri.port is not None:
File "/usr/lib/
return int(port, 10)
ValueError: invalid literal for int() with base 10: ''
Related branches
summary: |
- Uncaught error when using ssh password with / in + Parsing remote URIs fails when username or password contains ':', '@' or + '/' |
affects: | ubuntu → sbackup (Ubuntu) |
Changed in sbackup (Ubuntu): | |
status: | New → Confirmed |
Changed in sbackup (Ubuntu): | |
status: | Confirmed → In Progress |
summary: |
- Parsing remote URIs fails when username or password contains ':', '@' or - '/' + Parsing remote URIs fails when username or password contains ':', + '@','/' or '?' |
The same situation appears to happen with SMB connections as well - at least it does for me.
It fails with the exact same error message as above - lines 1625 of configgui.py and 193 of pathparse.py.
I imagine that it will with any of the selected protocols.
Maybe something with the path parser not expecting '/' before the @ symbol in the URL?