New answers tagged

0

In terms of security, it is better to have a whitelist approach rather than a blacklist. As Neil has clearly pointed out, you should only allow ports for incoming connections in your firewall that corresponds to the services that you are providing and need to accessed from the outside. Hope my answer helps you better understand the situation.


4

Assuming you're asking this in the context of Web Development... You can detect appropriate character sets with simple regex validation. However, you may also be falling victim to security theater: input sanitation is not the answer. If you are trying to validate for specific locales, and you don't want to accept any other locales, you can choose specific ...


4

Our answer is that for a truly international application, on general input such as people's names, you should accept everything and encode it at display time. Admittedly that (to some extent) passes the problem down to the guy writing the Encode algorithm. However, if you have an input that is a specific thing, such as a vehicle number plate, or a business ...


0

I think the term secure by default captures what you are looking for: In a network operating system, this typically means first and foremost that there are no listening INET(6) domain sockets after installation. That is, no open network ports. This can be checked on the local machine with a tool such as netstat, and remotely with a port scanner ...



Top 50 recent answers are included