February 02, 2014, 01:22:53 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
   Home   Help Search Login Register  
Pages: 1 [2]
Author Topic: Broken Pipe: solved?  (Read 28570 times)
Sr. Member
Posts: 363

(I am greg13070 on AWS forum)

View Profile
« Reply #15 on: January 07, 2008, 02:29:21 PM »

One small wish that I'd make for 1.2.5 would be potentially to include the location of s3sync.rb in the places that s3sync uses to look for the config file.

Why not just ln -s it to one of the search paths then?  I won't make the config search too promiscuous because I can see some kind of vuln where the script is fooled to look at the wrong config, and sends your secret data to someone else.  This wasn't an issue prior to 1.2.4 since the script only ran correctly when you were standing in the s3sync dir.  Now that it can run "from anywhere" there are extra considerations to have!
Posts: 6

View Profile
« Reply #16 on: January 08, 2008, 06:10:18 AM »

I'm only thinking of backward compatibility. You know....people who upgrade the script and don't test *everything* properly  - like me :-)  :-)

But yes, you are of course correct.

Pages: 1 [2]
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!