aMule Forum
English => en_Bugs => Topic started by: monkeyboy on March 07, 2005, 04:58:06 PM
-
Okay, so this is probably more of a feature than a bug, but it's really messing me up. I have a set of scripts that I use to manage amuled, which include invocations like "amulecmd -fc Shutdown". In the past, this was sufficient, and -f didn't require an argument. In the past few days, this changed, and even when I point it to .eMule, it still prompts for my password. My scripts don't work now!
I thought part of the reason to specify -f was to bypass the check if you had access to the config file. Has it been decided to nix this?
Monkeyboy
-
monkeyboy,
if you have CVS-20050307 you can do 'man amulecmd', (after proper installation, of course) and in previous versions at least 'amulecmd --help'. They are friends of you, and can be a great help.
In case you don't really understand them, (or maybe just being too lazy), do the following:
amulecmd -h -p -P -w
and then just remove all -f command-line options from your scripts. It will work, I promise you.
.eMule is not what amulecmd/amuleweb wants, they now use a separate config file.
I apologise for being rude to you, and I agree that this was a sudden and rude change, but it has to be made once.
Have a nice aMule experience, and, just to know, we always try keep at a minimum the number of 'incompatible changes'.
If you encounter any problems with it, just look for me on #amule at irc.freenode.net
-
Originally posted by GonoszTopi
if you have CVS-20050307 you can do 'man amulecmd', (after proper installation, of course) and in previous versions at least 'amulecmd --help'. They are friends of you, and can be a great help.
I had done this, actually, but I didn't read carefully enough because I thought I already understood it. I don't particularly like specifying the password in plain text on the command line, even once, since it means I then have to carefully edit my history files to keep my password out of it.
So, that minor complaint aside, you're right -- that worked. Sorry I didn't read the page more closely -- my bad.
Oh, and as an aside, I know you guys have been trying to keep compatibility. My aforementioned script system is a system that regularly downloads the new snapshot, builds it, shuts down the old amuled, and starts the new one. I couldn't do that if you weren't doing a good job, now, could I? :)
Thanks.
Monkeyboy
-
GonoszTopi,
I have current cvs running here, and I don't think amulecmd --help is clear enough. So please, be a little indulgent with the poor mortals. ;)
monkeyboy,
The format of the config file is text, so in principle you can create a minimal ~/.aMule/remote.conf file like this:
--------------------------------- cut here ---------------------------------------------
[EC]
Host=localhost
Port=4712
Password=22996e7cf159199daac3e1db71285eef
--------------------------------- cut here ---------------------------------------------
To get the password hash, do:
echo -n "myfucknpassword" | md5sum
I hope that amulecmd can read low caps hashes :P
Cheers!
-
Ok, ok, I admit I was just too angry (about other things) when I wrote that post.
Btw, phoenix, this isn't a solution to monkeyboy's problem, he still has to specify his password on the command line at least once. I'll create a solution for this problem.
-
GonoszTopi,
Ok, we all have bad days... :)
Sorry, I didn't get it, why isn't it enough to create the file? What did I miss?
Cheers!
-
Originally posted by phoenix
echo -n "myfucknpassword" | md5sum
It *IS* enough to create the file. The thing is, that to create the password hash, you have to specify plaintext password on command line at least once. Monkeyboy (and probably more users) wants to avoid this, because then he needs to edit his history file, to remove the plaintext password from everywhere on his system.
I'm working on a solution to avoid this "little" inconvenience.
-
Well, then we must do as passwd does. Ask for the password twice and do not echo.
-
No, I have a better idea.