I like you script, its simple and sweet. I only have to say that its probably not a good idea to advise people to chmod something to 777. This would enable other users (who would have access to your machine or network) to see not only the password which is hard coded in the script, but to change the script and insert something malicious. Perhaps something a bit more conservative like 700 would be a better choice. This value would mean that the owner (you) has read, write and execute permissions on the file, but no one else. I know you probably, and rightfully trust the people on your network, but hey–its the same amount of typing and you get free security .

Kind Regards,

Jesse

I like you script, its simple and sweet. I only have to say that its probably not a good idea to advise people to chmod something to 777. This would enable other users (who would have access to your machine or network) to see not only the password which is hard coded in the script, but to change the script and insert something malicious. Perhaps something a bit more conservative like 700 would be a better choice. This value would mean that the owner (you) has read, write and execute permissions on the file, but no one else. I know you probably, and rightfully trust the people on your network, but hey–its the same amount of typing and you get free security .

Kind Regards,

Jesse

crimeboy@groselia:~$ cat twi
#!/bin/bash
# requires curl
###########################

######## CONFIG
USER=YOULOGIN
PASS=YOURPASS
URL=”http://twitter.com/statuses/update.xml”
###############
curl -u $USER:$PASS -d status=”$*” -s -o /dev/null ${URL}

crimeboy@groselia:~$ cat twi
#!/bin/bash
# requires curl
###########################

######## CONFIG
USER=YOULOGIN
PASS=YOURPASS
URL=”http://twitter.com/statuses/update.xml”
###############
curl -u $USER:$PASS -d status=”$*” -s -o /dev/null ${URL}