what is web server hacking?

[nonmedcanada]

what is web server hacking?

[om2580]

it hack your server most of websites store valuable information.this has made them to attackers

[vikas_patel]

I agree with om2580.

[avvntech]

Web server hacking is a e-legal thing in web world. It may be use by terrorist. Server hacking removes all web security on your web store and stole all your valuable information from web.

[SerinaMAhren]

Every website stores their most vulnerable information as credit card number, e-mail address and password etc. When this all information and data get accessed by someone else over the internet then it called a web server hacking.

[sigmaseo]

It may be use by terrorist. Server hacking removes all web security on your web store and stole all your valuable information from web.

[zinist]

Hi,
Web server hacking means stole the all essential information/data which is stored on web server

[DarylSBeck]

Hacker is a term which refers to the person who cleverly cracks all the security system using some technologies and softwares and get all the data available on tht website.

[Bluesky94]

Web server hacking is a e-legal thing in web world.

[sigmaweb]

Web server hacking means all data renive from the SERP. you can slove this issue from web server and reupdate all website data.


Web Design Gurgaon

[alicewright]

Hope this link will help you to get your point. http://www.guru99.com/how-to-hack-web-server.html

[addisoncave]

It is developed by Microsoft. It runs on windows and is the second most used web server on the internet. Most asp and aspx websites are hosted on IIS servers. Apache Tomcat – Most Java server pages (jsp) websites are hosted on this type of web server.

[incomecracker]

Internet Information Services (IIS)– It is developed by Microsoft. It runs on windows and is the second most used web server on the internet.

[pablohunt2812]

I did a security workshop in a faraway land recently. I’ll not say which one because I want to ensure there’s an appropriate level of anonymity for this story as it could be rather inconvenient for the subject of it otherwise.
Anyway, I do my usual thing of showing attendees how to hack their own things. We do SQL injection and XSS and a whole bunch of other really hands on stuff targeted at developers. The niche I find myself filling these days is security content that talks to folks who actually build stuff and don’t live in security land where everything is, well, a little bit different. By no means do I mean that in a negative way, but security content produced by security people tends to end up talking their language and not resonating as well as it should with the folks who are primarily building rather than breaking. One of the very developer-centric things I do in my workshops is teach them how to use Fiddler to monitor (and modify) traffic between rich client apps and back end APIs. And that’s where it all started to get a bit interesting.
So we do this exercise where everyone proxies their phones through Fiddler (or Charles for the Mac folks) and identifies how their favourite apps are communicating with the back end. We talk about secure versus insecure patterns, how HTTPS can still be circumvented when you own the device and how terribly, woefully bad many of the apps we use every day are. We then go on and use Fiddler Script to modify responses from the server before they hit the device and of course everyone goes to their favourite shopping or real estate or car app and gets it to display a Ferrari selling for $50 (or something like that). One guy – a tester rather than a developer – goes back to his hotel room afterwards and tests an app his company builds. And that’s where it got really interesting…
It turns out his company makes software that controls very large agricultural machinery. They have a rich client app on a portable device which talks to an API back end. The device is provided to the good folks working the land with this machinery and they use it to autonomously control very big things that without saying too much and possibly leading to an uncomfortable discussion for the guy, are enormously expensive and could be caused to do serious damage if someone malicious could take control of them. Which is exactly what he found could be done; a lack of appropriate access controls meant that one customer could see and control another customers’ things. Remember now, these aren’t server things, they’re big moving things in “the real world”. He proceeds to tell the developers who apparently weren’t real happy with his discovery but I imagine they’d be even less happy had Farmer Joe figured out he could literally – physically – crash Farmer Bob’s things.
We spent about 45 minutes on this exercise and that’s all it took for the guy to have enough competency to identify a very serious risk. These issues are not rocket science, they’re well established risks for which technology pros simply need to learn the patterns. But this is often the way with security, in fact just this week at the Microsoft Ignite conference down here in Australia I shared this one:

[samim]

A web server, which can be referred to as the hardware, the computer or the software is the computer application that helps to deliver content that can be accessed through the internet. Most people think a web server is just the hardware computer, but a web server is also the software computer application that is installed in the hardware computer.