user6738237482

Unregistered less info
830 reputation
57
bio website
location
age
visits member for 4 years, 4 months
seen Jun 17 '10 at 17:21

Aug
9
awarded  Yearling
Apr
23
awarded  Yearling
Jul
10
awarded  Enlightened
Jul
10
awarded  Nice Answer
Apr
23
awarded  Yearling
Jan
20
awarded  Nice Answer
Apr
24
awarded  Yearling
Jun
21
awarded  Nice Answer
Jun
17
comment SSL handshake failed
serverfault.com/questions/151877/ssl-handshake-failed this is his other question which seems related. svn does not handle errors the same way that a browser does and is often much more terse. I incorrectly assumed that SSL was indeed working on the port and didn't test my theory before posting. I apologize for that. Feel free to flag my answer or downvote it and post your own answer if you have something to add.
Jun
17
revised SSL handshake failed
Unsure why a portion is bold even though I don't see any bold tags
Jun
17
comment SSL handshake failed
He was using svn rather than a browser and svn is a bit more picky. However, I am able to duplicate that error with SVN by disabling the SSL engine for port 443. While his apache is configured to answer for port 443, it is more likely that it is not answering as HTTPS, but rather answering HTTP on port 443.
Jun
17
answered outgoing DNS flood targeted to non-ISP hosts
Jun
17
awarded  Mortarboard
Jun
17
answered mdadm - Can't get RAID5 Array To Start
Jun
17
answered RewriteMap problem in .htaccess
Jun
17
comment Overriding Apache auth directive
That would be the problem then. Since index.php is within your authentication realm. What you might be able to do is put a symlink to index.php in an unprotected directory and do something like Alias /unprotected.php /path/to/symlinked/index.php and change your rewrite for the wdsl to use unprotected.php Your rewrite changes your authentication realm which is why your satisfy any/allow from all isn't working. It does actually work (I tested it here), but, when you do the rewrite, your other rules take over.
Jun
17
comment Server under DDOS attack - How to find out IPs?
IPs are very difficult to forge for web attacks. Since a valid web connection requires a syn/ack handshake, you'd have to be lucky enough to have the forged IP address ack with the right sequence number for your payload from the forged attacking site to work. UDP/ICMP traffic is connectionless and does allow forged packets, but, most hosts block those packets.
Jun
17
answered SSL handshake failed
Jun
17
answered Any way to make service do not autostart in Ubuntu/Debian, but leave K00 scripts in place?
Jun
17
answered Overriding Apache auth directive