John,
Another option you might consider instead of trying to pull the file
over an authenticated https connection is to use scp or a similar secure
transfer tool to get the iaxacl.txt file to the boxes. You could script
it the same way as you would the wget command.
I've never used 0.5, but I
Thanks for the offer. I am using the geni586 distribution, and most of
the machines in question are using the seldom seen 0.5 version, that
preceded the current 0.6 and 0.7 versions.
0.5 can't be remotely upgraded, due to ( at least ) a missing label on
the boot partition. it also is Asterisk 1.
John,
As long as all the nodes are the same architecture, you could build the
wget binary once and then just distribute it to all of them. I have the
full wget binary in my /mnt/kd/astcustom/root/usr/bin directory, and ran:
voip bin # ./wget -O /tmp/calltokens.txt --no-check-certificate
--http
Thanks for the reply, but that isn't an option in this case, as there
are 15-25 nodes that need this.
I'll have to dream up another way
John Novack
James Babiak wrote:
> John,
>
> I don't believe the busybox wget includes support for specifying a
> username or password. I tested it out on 0.7.2
John,
I don't believe the busybox wget includes support for specifying a
username or password. I tested it out on 0.7.2, with the same results.
You can always build the real wget package and put the binary on your
box if you need that option.
-James
On 09/28/2010 02:12 PM, John Novack wrote:
Any insight into the wget issue with the busybox used with AstLinux?
Attempting to pass a user name and password result in an error
wget -O /tmp/calltokens.txt --http-user=aaa --http-password=xxx
https://ckts.shaneyoung.com/secure/acl/iaxacl.txt
results in the error message :
w
