I used to be unhappy about this app until I found an SQL injection vulnerability that allowed me to log in and access the accounts of my previous dates by only needing to know their email addresses. This meant I was able to manipulate the ratings and comments people had made about me. Now I like the app :)
As the former CTO of that company, I really doubt this. When I was there, the app was built on Django, and I left some pretty competent people behind, so I'm quite sure they wouldn't have made a mistake so rudimentary.
However, I don't know what happened after I left, so there might have been some dubious decisions.
Facebook and Google have to do a lot of penetration tests to keep their security in tip-top shape, sure, they have a much larger attack vector in terms of code but my point is there:
Where there is public facing code, there is vulnerability.
Regardless of if you are built on Django, CodeIgniter, Rails or super-secret-obfuscated-language-mark-two, no application is bullet proof and it would be trivial for any highly skilled security tester to interface this way with your database.
Above you are essentially saying every application has SQL injection vulnerabilities and any good security guy will find them. This is a very specific and dubious conclusion to draw from the more general principle that there will be some vulnerability, somewhere. SQL injection specifically is quite easy to avoid. With some frameworks it would actually be rather laborious to introduce an SQL injection vulnerability. This is what Alexander is alluding to. This does not imply that applications are easily secured, just that this attack vector isn't what it used to be.
Well, statistics of pentests does show that, if tested, the vast majority of good quality, generally securely built applications have some vulnerabilities, and average applications have a huge multitude of vulnerabilities.
SQL injections are just one class of many. There are ways to vastly reduce SQL injection risks but that still leaves many other venues of attack.
No, I never have to be lucky at all. I literally can not put an SQL injection vulnerability into production unless I do so deliberately, my code wouldn't compile. Not everyone uses terrible rails style "lets automagically do shit behind your back so security holes are hidden from you" frameworks.
You're being too harsh. You seem to be talking about Haskell, so saying "not everyone" is a weird way to put it. You really mean a tiny fraction of people use Haskell to be safe in advanced ways. Well, Haskell is ahead of its time. Of course not that many people use it.
Even Haskell is not a silver bullet against every kind of security problem. Didn't Snap have a directory traversal bug a while back?
I don't understand what you are trying to convey. It appears like a deliberate red herring to try to distract from what I actually said. I personally use haskell, but you do not need to do so to get a complete guarantee against SQL injection. Nobody said anything about silver bullets or protecting against every security problem. I very clearly said SQL injection is a solved problem, in reply to someone claiming every single web app has SQL injection vulnerabilities in it and that any security researcher can easily sit down and exploit them, and the only way to deal with SQL injection is to be lucky over and over.
You are being too harsh (again). Whatever problems you deal with, whatever mistakes you make in your professional work, are also solved problems, using some technology that is unacceptable to you (probably for very good reasons).
You could have been informative and made your original point tactfully. Instead, you badmouthed a certain technology without even naming the stuff that was supposedly better. I'm a Haskell evangelist and agree with you 100%, and you came off like a jerk even to me.
I think perhaps we are operating with very different definitions of harsh. If your response is simply intended to be a poor attempt at criticizing my tone, you did not make that clear. Obviously such vacuous nonsense would not warrant a response.
Your assertion that whatever problems I deal with are solved problems is absolutely insane. Please, tell me how problems like interpreting customers requirements are "solved" and what technology I can use to ensure that all the code I write will 100% always match the users mental picture of what they wanted.
Criticizing the choice to deliberately create security holes for convenience is not "badmouthing", and "I'm offended" is not a productive response. It literally conveys no useful information at all.
Most vulnerabilities probably aren't due to the language but the application writers, simply because there are more eyes on the language than the application.
While I was there, we were building a social network for women, something between Path and Facebook where they could share their day-to-day with their closest friends. The rating thing was sort of an afterthought, I guess they pivoted.
There wasn't really a guy-hating culture, in fact, most of the employees there were men. I don't know how it's changed since.
> so apparently guys are still good enough to hire. Interesting.
I re-read the parent, and nowhere does it say nor imply that the CTO nor the people he hired were male. For all that we know, the site might be built by bimbos scratching one of their own itches.
I wouldn't bet on it, of course, but I'm amazed to see that prejudices are so deeply ingrained that:
His username is "StavrosK", and his full name, Stavros Korokithakis is in his profile. If you weren't familiar with the name Stavros and didn't know the gender, you could google it and the first link would take you to his website which shows his photo.
I don't see the 'deeply ingrained prejudice' here.
If there's one thing the internet has taught me, there is no such thing as ironclad code. OpenBSD still has security vulnerabilities, and I highly doubt Lulu's security chops are as good.
That said, I'm not trying to doubt the skill of Lulu's employees. Just warning that vulnerabilities are always a possibility.
Be careful with your trivial SQL injection, if the US police find out, that's 60 years behind bars, no access to a computer and daily "fun" in the shower.
I find it absolutely despicable to make light of violent abuse, including sexual abuse, in prison. We should be doing all we can to make our prisons safer for everyone.
The fact that many people think it is OK to make and laugh at prison rape jokes sickens me. What would you think if I made rape jokes about your 90 year old grandma? Or your ten year old son? Or your wife? If that is not ok, neither is prison rape of adult men.
I am appalled to realize many people think prison rape is part and parcel of the "prison experience". Should rape be used as a deterrent to unwanted behavior? Where do we stop? Will you be ok with teachers turning a blind eye on students raping other students in detention for not doing their homework or for misbehaving in the classroom? Answer me.
I don't think that this is a very reasonable response - making a joke and caring about something are not mutually exclusive.
Comedians regularly make jokes about some of the most abhorrent things that happen in the world. Racism, pedophilia, murder. Do you think that these comics therefore agree with racism, pedophilia and murder? No, of course not. They're making jokes.
It may not have been funny, and it may not have been appropriate (we're not in a comedy club after all), but it doesn't mean esquilax will be OK with "teachers turning a blind eye on students raping other students in detention for not doing their homework".
Basically, calm down, he made a bad joke, it's not the end of the world.
>Comedians regularly make jokes about some of the most abhorrent things that happen in the world.
Comedians who joke about raping women generally get booed and chastised and otherwise shunned. Comedians who joke about prison rape generally don't. Regardless of which you think is the appropriate response, it would be nice to see a little consistency.
This being said, I would like to point out that I also made light of violent, sexual abuse in prison in the grandparent post - I deserve the downvotes too.
I apologize for my rudeness. It was uncalled for and I really didn't mean it that way. I didn't mean to target you or put you on the spot. I understand that reforming people's views takes time. (I visited a freshman class in a South Asian university. If I was from there I presume I'd most likely think that cat calling women as they entered the classroom was normal and acceptable behavior.
I think we have a similar problem here. We've grown up with these jokes and lived with them for so long that it just doesn't bother us. I am glad you agree that prison rape is not OK. I am not trying to be sanctimonious (I actually had to look up that word). I just feel so helpless about this situation.
You can certainly feel the way you want to, but sticks and stones. Jokes make light of plenty of despicable things. That's the point of a joke: to make light of something.
A joke is a joke. Specifically naming someone is not a joke. It is personal and implies a thinly veiled threat. It's not apples to apples at all unless you are the personification of the concept of prison rape.
Do you live in the real world? Prisons aren't safe because they are full of violent offenders! It's pretty obvious that when you densely pack the bottom tier of society into small spaces that the outcome will be a whole load of violence - of all forms, rape (which is about power and control), gangs (which is core to the human species), fights and murder.
#1 on the list would be to stop sending so many people to prison, one way or another. Then you can afford to spend more resources per capita to better rehabilitate/reform/etc. the smaller number of inmates that remain.
IMO prisons should be about taking away peoples freedom, not about treating them like animals. But many people seem to be more concerned about their utility or lack thereof, for example if having a death sentence for death convicts costs more than life in prison or vice versa. Or the idea of having them work as effectively slave labour.
Thanks Lulu!