I discovered a while back that my SSH sessions weren’t staying active despite having the appropriate settings in
The other day, I found an article on Google with another way to get keep-alives working – luckily this seems to have worked perfectly.
You need to edit
~/.ssh/config (create it if it doesn’t exist), and add the following lines:
(I quit “
Terminal.app" just for completeness and it now keeps my sessions alive.)
Anurag Agarwal has posted a WASC Announcement about the Web Application Security Evaluation Criteria (WASSEC) Project on the application security blog. This really appears to be a unique effort – as it is a set of guidelines to evaluate web application security scanners on their identification of web application vulnerabilities and their overall completeness. It aims to cover things like crawling, parsing, session handling, the types of vulnerabilities and the actual information about those vulnerabilities themselves.
The goal of this project is to evaluate the technical aspects of the web application security scanners and *not* focus simply on the features provided.
Read More: http://myappsecurity.blogspot.com/2007/08/wasc-announcement-wassec-project-call.html
I always use vim when editing PHP files… but, I don’t have a good .vimrc.
About the only thing I have is the completion dictionary; provided by Rasmus:
or (as Wez stated), wget ‘http://viewcvs.php.net/viewcvs.cgi/*checkout*/phpdoc/funclist.txt’ -O php-funclist.txt
cat php-funclist.txt.new php-lang-constructs.txt | egrep -v ‘^#’ | sort | uniq > php-funclist.txt
that php-lang-constructs.txt has this in it:
# language constructs for completion, not found in the regular funclist
As, well as the PEAR coding standards:
Also, I show the line numbers by default:
I was thinking about adding SVN Commit and maybe PHP parser check with ‘!php -l %’
So, I guess what I am asking is if you use vim could you share your .vimrc