If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc).
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
The following Topic Prefixes are designated for use in Community Cafe:
DS (Distribution Showdown)
GN (Geek News)
KLD (Kubuntu or Linux Discussion)
TWC (The Water Cooler)
KUT (Kubuntu User Testimony)
NRD (Next Release Discussion)
While use is not required, doing so allows for efficient Filtering.
I think a better method would be to bind mount the location you want to store the www file in to /var/www. That way you keep apache inside that directory rather then being able to access any file on your system (better to be safe then sorry later when it comes to exposing things to the internet).
I was under the impression that even folowing system links that apache could not leave the linked to location , unless of course there was a link in that location and so fort and so on ?
If you're really interested in this stuff, I can recommend http://camendesign.com/code/video_for_everybody
It's a bit old but still one of the best tutorials, with a fallback for browsers not able to handle <video>, without the use of flash.
yes that's a nice slightly more in depth right up on it .
and is what I did ,,,,,,only just the part for .webm and dropped all the stuff for a download and flash and other formats .
this from the access log , last time I put up a web server I got a bunch of this stuff as well and some times large blocks of stuff like x686x686x686x696x696 over and over and over agin ,,,,,,,?
ya for a split second I thought of flooding that IP ,,,,,but naw I ante so shallow
Rarely is "attacking back" a good idea. Many attacks are laundered through unsuspecting third parties, and what appears to be the origin really isn't. If the third party were to eventually analyze their problems, they'd be hard pressed to distinguish you from the real attacker, and you could be charged for computer fraud and abuse.
Rarely is "attacking back" a good idea. Many attacks are laundered through unsuspecting third parties, and what appears to be the origin really isn't. If the third party were to eventually analyze their problems, they'd be hard pressed to distinguish you from the real attacker, and you could be charged for computer fraud and abuse.
but of course you are correct,,,,,,,,,,,it's just that initial reaction to reach out and slap some one .......
But you could look up the ip and try contacting them to tell them you have seen suspicious behaviour form their ip (or contact their isp). Hopefully they can do something about it.
Comment