you are viewing a single comment's thread.

view the rest of the comments →

[–]Vulptex 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (2 children)

If you're going to use your webserver in actual production, and you're worried about attacks, you probably shouldn't be using C. Not because of the typical lame excuses people use these days like "it takes an extra 5 seconds compared to higher level languages!" It's because the lack of safety is a huge security risk. Companies using C servers always get hacked, and sometimes the attacker can even do arbitrary code execution. This is because the smallest oversight will cause "undefined behavior". This is usually no big deal in a client program, because it merely causes bugs. But hackers abusing it intentionally can do some serious damage.

It's probably not a bad idea to write some of the server-side programs in C or some other language depending on what you're trying to do. But definitely not for the API or anything interacting with the user.

[–]chickenz[S] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (1 child)

C processes characters very well.. the problems that come up in c is usually some kind of buffer overflow issue..

..and, this server has one purpose and one purpose alone.. to display a snapshot of my trading server and to refresh every ten seconds.

i dont personally give a fk what you think about C, cuz i have been spinning C code since 1991.. omg.. i had a job writing C programs when i was in jail in 1993.. i wrote programs by hand for a client BY HAND on paper and mailed them to my client.. they were perfect every time.

http://ecoq5i5xokjqe4ckfofvw3n72zqz224uktpbtjyptuvydfr6wckeanyd.onion

[–]Vulptex 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

Is it just me or have 95% of saidit users been in jail at some point?