|
Security Mode
|
Description
|
Versions supported
|
|
1
|
No
Security. Device operates in promiscuous mode allowing any other Bluetooth
device to connect it
|
v2.0
and earlier devices support it.
v2.1 and later devices support for backward compatibility. |
|
2
|
Service
level enforced security. Security measures are established after the channel
is established. Supports Authentication, Authorization and Encryption.
|
v2.0
and earlier devices support it.
v2.1 and later supports for backward compatibility . |
|
3
|
Link
level enforced security. Security measures are established before the
channel is established. Supports authentication and encryption.
|
v2.0
and earlier devices support it.
but v2.1 and later devices support for backward compatibility. |
|
4
|
It
is a service level enforced security mode in which security procedures are
initiated after link setup. Uses SSP (Secure Sample Pairing)
|
Mandatory
for communication between v2.1 and later BR/EDR devices.
Backward compatible with any of the other three Security Modes. |
Sometimes, during file upload we come across situation wherein there would be check on the file extension at the client side as well as server side too. If the application does allow only .jpeg extension to be uploaded, the client side java script checks for the extension of the file before passing the request. We all know that how easily this can be defeated. Some applications, checks for the extension at the server side also. That's not easy to bypass. However there are some ways with which it still can be bypassed. Most of server side scripts are written in high level languages such as Php, Java etc who still use some C/C++ libraries to read the file name and contents. That leads to the problem. In C/C++ a line ends with /00 or which is called Null Byte. So whenever the interpreter sees a null byte at the end of the a string, it stops reading thinking it has reached at the end of the string. This can be used for the bypass. It works for many servers, specially php servers. T...
Comments