Using fdx for sending information

[Manuales]

I have a problem ..
currently for sending information using the command fdx i use the foolowing:

fun_secure_transport_file_driver_fdx a A aet girl1:1@$rtu#"@patito.com

fun_secure_transport_file_driver_fdx :
It is a function
a, A aet are names

aet is the name of the file to be sent.

girl1:1@$rtu#"@patito.com is for sending theinformation.

girl1 --> user
1@$rtu --> password
patito.com --> server to deliver the information

question
how can i do to avoid the system understand the first "@" as part of the password and not part of the domain ?

here here
girl1:1@$rtu#"@patito.com


for $ i know i can use "\" right?

please let me know.
Regards.

[Mel Burslan]

if you are using hpux system, you can not have @ character in your password file, if this user is to be authenticated via /etc/passwd file. If the password string is to be handled by application, yo might be able use it and as with any other special character, you can escape it by placing a "\" (backslash) in front of it.

[Manuales]

Wel ..
yes, i'm using hp-ux server ....

in my understanding:

the way for sending information from hp-ux to other server using fdx and having the remote link is the following:

fdx -u test.doc https://girl1:1@$rtu#@patito.com

where fdx --> command to send the information
test.doc ---> file to be sent
girl1 --> user of the remote server
1@$rtu# --> password
@patito.com --> DNS of the remote server

the problem here is that the system thinks that in the first at "@" starts the DNS,when it is part of the password ... so, i need to know how to tell to the system that is part of the password and the second at "@" there starts the Domain ...

please let meknow.
Thanks.

[Mel Burslan]

if patito.com is another hpux server, and password you are using is compared against the password hash of user girl1 on that side, you can not use neither @ nor # as part of the password.

If the above statement is not true, then try adding backslash in front of @, $ and # signs and see if it works. If not, you need to give a little more information about this fdx application.

Also do you have any control over this patito.com server ? which OS is it running ?

[Manuales]

no, i wrote an "\" before those signals and it did not work ...


fdx is similar to ftp .. it is a tool to send information ...

does someone of you knows to use this tool?

[Mel Burslan]

what operating system is this server patito.com running on ?

[Manuales]

i do not know :(

[Mel Burslan]

so basically you are neither sure if your hpux machine is sending the right username:password nor patito.com is receiving what you sent properly. Well, I can suggest one more thing that I am not an expert on. If the fdx utility is not using an encrypted communication between your hpux machine and patito.com, use a network sniffer to see if the password is leaving your machine as you expect them to look like. If it is so, you need to contact the patito.com server admins to check what is wrong with it.

Are you able to login using an interactive method instead of using the whole sha-bang from a single command line entry ? Has it ever worked from this hpux machine ? If it did, what changed since then ?

[Manuales]

the user and pass are correct, the remote server im not sure if it is a unix server ...i think yes ...
basically i want to know programming , i mean:

the problem here is that the system thinks that in the first at "@" starts the DNS,when it is part of the password ... so, i need to know how to tell to the system that is part of the password and the second at "@" there starts the Domain ...


please

[blah2blah]

more then likely the utility is using the "@" as a field seperator between user and host. which means you can not use "@" as a password character.

you can verify this by changing the password, or if you don't specify a user/password the utility will ask you to provide the information.

[Manuales]

yes ..
how can i do that for the system ask me the information???

[Dennis Handly]

>the problem here is that the system thinks that in the first at "@" starts the DNS, when it is part of the password ... so, I need to know how to tell to the system that is part of the password and the second at "@" there starts the Domain ...

There may be no way to do that.
I was thinking if these are URLs you might be able to use "%40" for "@". But I don't know if those are first converted to "@" before looking for the "@" separator.

>how can i do that for the system ask me the information???

Typically a browser will ask you.

[blah2blah]

>how can i do that for the system ask me the information???

The URL can include your username and password, in the form

://:@/

Otherwise, you wll be prompted for a username and password when you make the connection to the remote server.

so, don't put the user/password information on the commandline and you'll be prompted

[OldSchool]

see this:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1220826

note that the $rtu when used as you showed will be evaluated (probably not set) resulting in a blank.

some combination of '$rtu', backslashes or multiple backslashes can probably make this work.

fdx -u test.doc https://girl1:'1@$rtu#'@patito.com

might also work...although changeing the password on the destination would probably be best.

[OldSchool]

Manuales:"the problem here is that the system thinks that in the first at "@" starts the DNS,when it is part of the password ... so, i need to know how to tell to the system that is part of the password and the second at "@" there starts the Domain ..."

not quite. that distinction is being made by "fdx", not "the system". Also, you need to understand that whatever shell you are running on the HPUX end may be: a) making substitutions in the command line that you don't want to happen, and b) the stty setting may or may not be having an effect (for example on some terminals and unescaped "@" wipes the line, and c) what, if anything the "fdx" command itself interprets as special.

From the appearance of the password in use, I'd guess that the receiving end is Windows, as most UNIX admins wouldn't use a password with those characters for the reasons you are finding...they can be difficult to work with.

I'd suggest you look at single quotes around the password first, then backslashes, and then combining them.

Note that if you get it working from the command line (if ever) you may face more issues if you try and script it, especially if you need to use backslashes. You may end up needing two backslashes in the script for every single backslash you had on the command line.