thread closed - staffs pls delete

[Plоt 6]

---

[thread colsed]

[0VertexPlayz0 0]

Thanks! I was looking for this everywhere!

[anthonyR013 0]

great man, this was needed a long time ago

[textverified 0]

It's easy to tamper with data on the client side and you're fighting a losing battle. if you need to protect the integrity of your application, traffic, data, anything, you must do it server side. Period.

[98657456 0]

It's easy to tamper with data on the client side and you're fighting a losing battle. if you need to protect the integrity of your application, traffic, data, anything, you must do it server side. Period.

 

Well even though, .NET is highly vulnerable in terms of unpacking.

So you could basically "bypass" the login system if you're using PHP requests and stuff like that.

[textverified 0]

It's easy to tamper with data on the client side and you're fighting a losing battle. if you need to protect the integrity of your application, traffic, data, anything, you must do it server side. Period.

 

Well even though, .NET is highly vulnerable in terms of unpacking.

So you could basically "bypass" the login system if you're using PHP requests and stuff like that.

 

You cannot bypass the authentication and authorization if it occurs server, side short of exploiting unpatched vulnerabilities and compromising the server itself. That's like saying you can write some special client that will bypass Google's auth/login servers. Not happening.