Won't accept <email address hidden>@demon012.com as an username and password

Bug #109474 reported by Alan Jenkins
2
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned

Bug Description

Ubuntu Version: Fiesty Fawn
bzr Version: 0.15-0ubuntu2

My webhost has made it so that when I create a FTP account that is not <email address hidden> that I have to include the @demon012.com as part of the username. However bzr does not like this and crashes as a result output is shown below:

bzr init ftp://<email address hidden>@demon012.com
bzr: ERROR: socket.gaierror: (-2, 'Name or service not known')

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 650, in run_bzr_catch_errors
    return run_bzr(argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 612, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 304, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.5/site-packages/bzrlib/builtins.py", line 1258, in run
    to_transport.mkdir('.')
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/ftp.py", line 351, in mkdir
    f = self._get_FTP()
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/ftp.py", line 141, in _get_FTP
    self.is_active)
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/ftp.py", line 68, in _find_FTP
    conn.connect(host=hostname, port=port)
  File "ftplib.py", line 117, in connect
    for res in socket.getaddrinfo(self.host, self.port, 0, socket.SOCK_STREAM):
gaierror: (-2, 'Name or service not known')

bzr 0.15.0 on python 2.5.1.candidate.1 (linux2)
arguments: ['/usr/bin/bzr', 'init', 'ftp://<email address hidden>@demon012.com']

** please send this report to <email address hidden>
alan@alan-desktop:~/test$ bzr init ftp://<email address hidden>@demon012.com
bzr: ERROR: socket.gaierror: (-2, 'Name or service not known')

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 650, in run_bzr_catch_errors
    return run_bzr(argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 612, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 304, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.5/site-packages/bzrlib/builtins.py", line 1258, in run
    to_transport.mkdir('.')
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/ftp.py", line 351, in mkdir
    f = self._get_FTP()
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/ftp.py", line 141, in _get_FTP
    self.is_active)
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/ftp.py", line 68, in _find_FTP
    conn.connect(host=hostname, port=port)
  File "ftplib.py", line 117, in connect
    for res in socket.getaddrinfo(self.host, self.port, 0, socket.SOCK_STREAM):
gaierror: (-2, 'Name or service not known')

bzr 0.15.0 on python 2.5.1.candidate.1 (linux2)
arguments: ['/usr/bin/bzr', 'init', 'ftp://<email address hidden>@demon012.com']

Changed in bzr:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Martin Packman (gz) wrote :

@ is not permitted *within* the userinfo, it delimits it from the host.

http://tools.ietf.org/html/rfc3986#section-3.2.1
  userinfo = *( unreserved / pct-encoded / sub-delims / ":" )

Correct URL would be ftp://alanproject%<email address hidden>/

Suggest close as INVALID or turn it into "throw useful error on invalid URLs".

Revision history for this message
Bubba Siggler (bud3) wrote : Re: [Bug 109474] Re: Won't accept alanproject@demon012.com@demon012.com as an username and password

On 6/4/07, Martin <email address hidden> wrote:
>
> @ is not permitted *within* the userinfo, it delimits it from the host.
>
> http://tools.ietf.org/html/rfc3986#section-3.2.1
> userinfo = *( unreserved / pct-encoded / sub-delims / ":" )
>
> Correct URL would be ftp://alanproject%<email address hidden>/
>
> Suggest close as INVALID or turn it into "throw useful error on invalid
> URLs".

Hi everybody,
I was having like I need to get some sutf tag for the library dict. When I
got back to the pc did I leave the dict open. I hope not need some help if
possible

best regards

bubba

--
> Won't accept <email address hidden>@demon012.com as an username and
> password
> https://bugs.launchpad.net/bugs/109474
> You received this bug notification because you are a member of Bazaar
> Developers, which is the registrant for Bazaar.
>

--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFkcN7yXWcajQQndYRAgbqAKCMyXN9Jx4g0X7jocg+aUSFz0x4LwCgrURW
eGtqLjpzQVYa9+gzpCRtB84=
=zrpM
-----END PGP SIGNATURE-----

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 109474] Re: Won't accept alanproject@demon012.com@demon012.com as an username and password

Its true that a normalised URL cannot have user@host@host. However user
interfaces commonly take pseudo URL's and normalise them before handing
off to actual protocol implementations.

As long as we do the right thing on a normalised URL I have no problem
with a minor heuristic like this being supported, and I think its a
niceness for users in such circumstances not to have to know the details
of URI escaping.

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Revision history for this message
Q (louwrentius) wrote :

Due to this little bug, we cannot use bazaar in our environment since our corporate ftp-server uses username@domain-style usernames. It would be nice if bazaar could handle this.

Revision history for this message
Vincent Ladeuil (vila) wrote :

@Q:

Until the bug is fixed, the work-around is to use:

  username%40domain-style

instead of:

  username@domain-style

You *can* use bazaar :)

Revision history for this message
John A Meinel (jameinel) wrote :

So... he's using a really old version of bzr (0.15), I'll note that this bug was fixed in bzr 1.6 as part of bug #228058. In fact, I'm going to mark this as a duplicate of that bug.

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.