Apache.org defaced - Security archive case study
blog.sucuri.net
Apache.org defaced - Security archive case study
1–7 of 7 posts
Re: Apache.org defaced - Security archive case study
#2Re: Apache.org defaced - Security archive case study
#3More like a lessons learned from the Apache defacement.
Re: Apache.org defaced - Security archive case study
#4More like a lessons learned from the Apache defacement.
"Lessons learned from the Apache.org defacement of 2000" would have been a pretty good title. I still would have clicked, but my expectations would have been differently calibrated. As the title was written, I was expecting Apache.org to be, currently, defaced.
Re: Apache.org defaced - Security archive case study
#5More like a lessons learned from the Apache defacement.
"Lessons learned from the Apache.org defacement of 2000" would have been a pretty good title. I still would have clicked, but my expectations would have been differently calibrated. As the title was written, I was expecting Apache.org to be, currently, defaced.
Re: Apache.org defaced - Security archive case study
#6Earlier quoted context omitted.
"Lessons learned from the Apache.org defacement of 2000" would have been a pretty good title. I still would have clicked, but my expectations would have been differently calibrated. As the title was written, I was expecting Apache.org to be, currently, defaced.
The "from 2000" is not really relevant -- all the same technologies are in use and are likely misconfigured in the same way. There are probably 100s of sites on the Internet that could be owned in the way the article describes.