Skip to content
0:00 / 0:00

#secureprogramminglanguages#taintanalysis#popl

What is a Secure Programming Language?

ACM SIGPLAN

11K subscribers • 53 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Cristina Cifuentes

Intermediate. Assumes working knowledge.

2.2K views6 years ago2 recommendations

Programming languagesSecurityLanguage design and type systemsWeb and application security

Cristina Cifuentes discusses language features that can prevent security vulnerabilities, such as using type systems to track tainted strings.

Presented by Cristina Cifuentes. Presented at POPL'20

Why it's here

2 people recommend this

What people say. Recommended as an interesting talk on language features like tainted types that can prevent real-world security bugs.

u/bruciferNomsu.orgin r/ProgrammingLanguages • Recommends

On “What programming language features would have prevented or ameliorated Log4Shell?”

You should take a look at the talk What is a Secure Programming Language?, which discusses some interesting language features relating to security. Specifically, the idea of having "tainted" or "untainted" strings. The basic idea is to have all user input methods return strings with a `TaintedString` type and throw a type error if you pass a tainted string to an API that requires an untainted string. Then, you can provide a mechanism to convert tainted strings into regular strings, either by escaping them or by manually flagging them as safe. This helps you avoid security bugs caused by forgetting to sanitize user input. You can always circumvent the safety rails, but you have to conscious…

u/bruciferNomsu.orgin r/ProgrammingLanguages • Recommends

On “What features would you want in a new programming language?”

> I want a language that makes oncall less of a hell. There's a great talk on this, What Is a Secure Programming Language?. In the talk, the speaker cites information from the national vulnerabilities database that roughly half of all the real-world security bugs fell into the categories of: buffer errors, code injection, or information leaks. As we've shifted away from using memory-unsafe languages like C, the percentage of buffer errors seen in the wild have accordingly dropped. The other two areas (code injection and information leaks) are also within the domain of "things programming languages can solve or mitigate", although we haven't yet converged on solutions to them like we have…

u/tluyben2in r/ProgrammingLanguages • Recommends

On “Features or use cases that could make a programming language unique”

Yes, voting for this one! I have been fascinated by this for ages. My job requires me to make sure these things happen (PCI/GDPR etcetc) and there is really nothing but your own rigor, pen testing and audits to prevent things from going wrong. We solved a lot with types, but that's still really not nearly as good as it could be. Anyone know of other projects working on this? I saw a youtube of someone presenting this for Hermes but also another project; I don't remember if it was strangeloop or popl or another, but I cannot find it. Edit: Think it was [video

u/bruciferNomsu.orgin r/ProgrammingLanguages • Recommends

On “Interested in "secure programming languages", both theory and practice but mostly practice, where do I start?”

I would recommend the talk "What is a Secure Programming Language?" by Cristina Cifuentes.