|
László Szekeres
@
lszekeres
New York, NY
|
|
Securing C/C++ at Google.
|
|
|
18
Tweetovi
|
183
Pratim
|
110
Osobe koje vas prate
|
| Tweetovi |
|
|
László Szekeres
@lszekeres
|
1. stu |
|
Thanks, Caroline! Yes, let me send an email including everyone.
|
||
|
||
| László Szekeres proslijedio/la je tweet | ||
|
Moshe Vardi
@vardi
|
15. ruj |
|
PhD :-) pic.twitter.com/FrXGvXssqS
|
||
|
|
||
| László Szekeres proslijedio/la je tweet | ||
|
Fish in a Barrel
@LazyFishBarrel
|
3. ruj |
|
This account's primary purpose is to complain about memory unsafety, but what areas of research could make memory safe languages easier to adopt and even more safe? One of FiaB's principals tackles the topic: alexgaynor.net/2019/sep/02/me…
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
2. ruj |
|
Really enjoyed @FSEconf last week and very excited and honored that our paper on test driver generation for #fuzzing received Best Paper Award of the #esecfse industry track!
See the paper here: ai.google/research/pubs/… pic.twitter.com/1SBiN9M9mk
|
||
|
|
||
| László Szekeres proslijedio/la je tweet | ||
|
John Regehr
@johnregehr
|
19. kol |
|
new blog post: Write Fuzzable Code
blog.regehr.org/archives/1687
in which I express a lack of sympathy for anti-fuzzing measures
|
||
|
|
||
| László Szekeres proslijedio/la je tweet | ||
|
Tamás Görbe
@TamasGorbe
|
5. kol |
|
A Mathematician's Way* of Converting Miles to Kilometers
• 1 mi ≈ 1.609 km
• The ratio of consecutive Fibonacci numbers Fₙ₊₁/Fₙ tends to the golden ratio φ ≈ 1.618 as n increases
So Fₙ mi ≈ Fₙ₊₁ km
*This is how I do it 😅 pic.twitter.com/Jbuwj6rDC1
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
7. kol |
|
You might also be interested in our recent paper in this area: ai.google/research/pubs/…
|
||
|
|
||
| László Szekeres proslijedio/la je tweet | ||
|
ESEC/FSE 2019
@FSEconf
|
6. kol |
|
#esecfse19 is happy to feature the industry paper "FUDGE: Fuzz Driver Generation at Scale" by Domagoj Babić, Stefan Bucur, Yaohui Chen, Franjo Ivančić, Tim King, Markus Kusano, Caroline Lemieux, László Szekeres, and Wei Wang. Moreat esec-fse19.ut.ee/program/overvi…. @FSEConf, @UniTartuCS pic.twitter.com/vFVInmDbDV
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
5. kol |
|
Nice! Congrats! You might be interested in our recent paper in the area: ai.google/research/pubs/…
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
28. srp |
|
Write unit testable code. Whenever it makes sense, in addition to unit testing an interface, also fuzz it.
|
||
|
|
||
| László Szekeres proslijedio/la je tweet | ||
|
Max Moroz
@Dor3s
|
25. srp |
|
The legendary AFL fuzzer developed by @lcamtuf is now on GitHub: github.com/google/AFL #fuzzing #afl #nevergetsold
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
15. srp |
|
We are very grateful too for your great contributions! :)
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
15. srp |
|
Fuzz Driver Generation at Scale!
Check out the preprint of our @FSEconf paper at: ai.google/research/pubs/…
work w/ D. Babic, @sbucur, Y. Chen, @fivancic, T. King, M. Kusano, @cestlemieux, W. Wang.
See you at @FSEconf in August! #esecfse #google #fuzzing #ossfuzz
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
11. lip |
|
Nice work! BTW I just missed you guys, I was there for deeptestconf.github.io but left after that :/
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
2. tra |
|
🇭🇺Hungarian: Feed the goat and keep the cabbage too.
|
||
|
|
||
| László Szekeres proslijedio/la je tweet | ||
|
Google Open Source
@GoogleOSS
|
9. sij 2019. |
|
Are you fuzzing? OSS-Fuzz, free continuous fuzzing infrastructure that we offer to open source projects, has discovered 9,000 bugs since December 2016!
Help us make open source more secure: apply to integrate your project. goo.gl/hVS7Zu
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
30. stu 2018. |
|
Klassz járgány!
|
||
|
|
||
|
|
László Szekeres
@lszekeres
|
7. stu 2018. |
|
Yes! We are working on automated fuzz target generation to help bring the benefits of fuzz testing to more projects. These targets exercise libraries similarly to typical client code in other projects. This increases the likelihood of finding bugs that OSS developers care to fix.
|
||
|
|
||