ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kerem Gurbey <>
Subject SCP Bug Fix
Date Thu, 10 Oct 2019 17:20:51 GMT

I wanted to suggest a change for parseUri function in (and other
files that would be affected from the change).

Basically, the problem I have observed are the same problems mentioned in
Bug-58128 <> with the
Scp class. Nowadays, both user names and path names are allowed to include
'@' and ':' characters, which causes parseInt function in Scp class to set
user name, host name, and many other parameters wrong.

The solution I am suggesting is a check for determining if the
user/programmer has already set the values for the class variables that
parseInt function tries to modify before they called "execute" on the Scp
object they created. Mainly, if the username, host name, and either one of
password or key file information are already provided (i.e. the related
fields are already modified) before the call to the "execute" method, then
in the following call to the "parseInt" method caused by "execute",
"parseInt" should treat the passed-in "uri" string as the value of the
remote path itself, and just return it. By this way, we also leverage the
use of "setUsername", "setHost", and "set Password" methods on an instance
of Scp class.

Please let me know if the solution sounds feasible. I can also create a
pull request for this.

Best Regards,


*Kerem Gurbey*

Software Engineer


Cisco Systems, Inc.

303 Second Street, North Tower


San Francisco



United States

This email may contain confidential and privileged material for the sole
use of the intended recipient. Any review, use, distribution or disclosure
by others is strictly prohibited. If you are not the intended recipient (or
authorized to receive for the recipient), please contact the sender by
reply email and delete all copies of this message.

Update Profile <> - Unsubscribe
<> - Privacy

Please click here
for Company Registration

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message