"You should use Windows server!"

It was a high security project which needed to run very stable. Even the windows sysadmin looked at that guy like 'dude what the actual fuck'.

because sharing is caring! spread the word and always remember to share your data :p

Well maybe it's a .Net project?

@xotu sorry but for a high security project windows is a no go for me! (and dot net core runs on linux as well now)

@linuxxx you gotta be aware from DotNet Core, in v1.x I read there are security risks in ASP.Net core, didn't read if they were fixed in v2 release, but better hold off for a while on projects where security is a must and you cannot afford any risks

@xotu It was PHP/Node though :)

@linuxxx The Windows sysadmin is the same one from a previous rant?

@gitpush what security risks? That's vague and a half lol

@iam13islucky https://github.com/dotnet/...

@gitpush it's been fixed for a bit now. 2.0 is officially out now, this was fixed in patches for 1.0 and 1.1. No need to act like that is still a thing.

Mh stackoverflow use Windows. Is it really that bad?

https://meta.stackexchange.com/ques...

Why does windows still come in consideration?

*Facepalm*
*BIG sigh*

@Qaldim Think So yeah!

@linuxxx wait I thought you gave this advice jokingly one time and then the other guy said no way.
Lol I'm sure it was probably another instance, you seem like the type of dude to dabble with all kinds of servers day and night 😅

Windows Server is actually locked down nicely, it's usually user error that allows me to get a foothold during an engagement.

@linuxxx the fact that they thought a PHP/node app could be secure or stable is hilarious, period.

@er1n If you program using safe practices, I don't see why it couldn't be secure?

@linuxxx that's true, but I don't have much faith in this place given your post

@er1n May I add that I was the person who was going to develop the backend and suggested PHP/Node? :)

@er1n Oh and the place was awesome, that intern was just an ass.

@linuxxx oh, I'm just generally leery of anything that touches PHP at this point, after working on some codebases that had such lovely features as "unsalted md5 for password hashes", "evaling cookies to maintain state", and "dumping arrays to text files as a database"

@er1n😲😷 that''s just bad code/security practice in general 😩

@er1n hmm, how does one even dump an array to a text file, I wanted to do that s while back but ended up json encoding it instead.

For the record, I wanted to dump lt, so I could copy paste the content into a repository.

@lotd most primitive arrays could be turned into a CSV file, right?

@iam13islucky yes, but then it's not an array dumped to a file.
Afaik at least.

The whole point for me dumping an array to file was to easily copy paste some stuff :p

@lotd ah. I don't know how well dumping the memory contents would work, but I see where you are coming from

@er1n we had plain text passwords in a Perl application (authentication service) I actually had to fight over it with the senior Dev to fix that crap in the new version. Doesn't make Perl a bad language though (has plenty of other traits for that 😂).

Storing data (array) in PHP files is actually not be such a bad idea. With opcache this is the fastest way to read data in a PHP app. Not so great if it needs a lot of updates though.

@babeman Using PHP for the website and node for the general application :)