Stijn Volckaert

180 posts

Stijn Volckaert

Stijn Volckaert

@StijnVolckaert

Associate Professor @KU_Leuven @DistriNet. Working on Systems Security. Anti-Cheat Developer. Ethical Hacker. Maintainer of Unreal Tournament for OldUnreal.

Ghent, Belgium Katılım Ekim 2017
198 Takip Edilen194 Takipçiler
hacker.house
hacker.house@hackerfantastic·
@sev305001538593 Thanks, have team member for handling security reports contact me (matthew AT hacker dot house) and I will send bug reports to them. I use games like Quake3 to demo exploit dev as they provide good learning experience for students. I will likely find more. cc @StijnVolckaert
English
1
0
0
27
Stijn Volckaert retweetledi
Mathy Vanhoef
Mathy Vanhoef@vanhoefm·
After an embargo of 8 months, we are glad to finally share our USENIX Security '25 paper! We found more than 4 MILLION vulnerable tunneling servers by scanning the Internet. These vulnerable servers can be abused as proxies to launch DDoS attacks and access internal networks.
English
5
77
189
23.6K
Stijn Volckaert
Stijn Volckaert@StijnVolckaert·
I'm in this picture and I like it 😁
ACSAC@ACSAC_Conf

Congratulations to this year's second #ACSAC2024 distinguished paper award winners: André Rösti, Stijn Volckaert, Michael Franz, Alexios Voulimeneas 👏👏👏 The talk "I’ll Be There for You! Perpetual Availability in the A8 MVX System" is Thursday in the "System Security" session!

English
1
0
8
231
Stijn Volckaert retweetledi
Matthias Dobbelaere-Welvaert
Matthias Dobbelaere-Welvaert@DOBBELAEREW·
We mogen verdorie als land trots zijn op topexperten zoals @bpreneel1 (en COSIC) en de vele andere Europese stemmen die de draak van #ChatControl hebben tegengehouden. Maar je ziet: de nieuwe directeur van Child Focus & BFF Annelies proberen het toch gewoon opnieuw.
Nederlands
2
20
136
3.2K
Stijn Volckaert retweetledi
BlackRoomSec
BlackRoomSec@blackroomsec·
Please share this far and wide. As far and wide as you can. NIST Password Guidelines for 2024 are in the process of being updated. This is a HUGE pet-peeve of mine (when vendors in particular are still operating like its 2017 and keep changing passwords every 60 days, STOP DOING THIS, it's outdated and has been shown to put you MORE at risk than less -- NIST explains why it does in this document, meticulously outlining user behavior**) so I'm sharing this in the hopes all of you will pass it along to your bosses. The Special Publication series governing passwords is SP 800-63 "Digital Identity Guidelines". The 2024 version is 800-63-4. Here: pages.nist.gov/800-63-4/ The companion docs are also on that link. They are 800-63A, 800-63B and 800-63C. These are different documents for different scenarios in play at your org. The previous update was in2020. The changes in the 2020 version from the 2017 version were numerous but one of them was that the password verification method should NO LONGER require passwords be changed at specific intervals (i.e. every 60 days) but in the following circumstances instead: 1. After a breach/compromise 2. User request 2024 repeats this and adds a bunch more guidlines but here is a screenshot of page 13 of the new 800-63-4 (note the # 4 after it) which outlines how your systems should now and moving forward, be handling passwords. This goes for Active Directory, too. All your systems which have passwords should align with these guidelines provided there isn't another standard or framework you must adhere to which overrules this. Most frameworks, however, have moved away from arbitrary password resets and complexity rules. **We cybersec researchers and hackers use wordlists from breaches in a variety of different ways. Hackers use them in tooling to crack passwords whereas researchers use breach dumps to see the kinds of passwords users are creating and the psychology behind them. Using complexity rules gets you the user psychology of: Password1 Password2 and so on Use phrasing instead and allow for spaces, which is important. Humans type phrases with spaces. They also mention phish-resistant methods and most vendors are on-board with MS going to be turning off all Legacy Auth next month, across all free accounts and tenancies. I'm so excited for the new changes! Ok I'm off my soapbox. Share the love! Thank you!
BlackRoomSec tweet media
English
186
1.8K
5.5K
645.3K
Stijn Volckaert retweetledi
USENIX WOOT Conference on Offensive Technologies
Did you think to be safe with store-only bounds checking? Definitely something to reconsider after reading the paper “Not Quite Write: On the Effectiveness of Store-Only Bounds Checking” by @a3_jacobs #woot24
USENIX WOOT Conference on Offensive Technologies tweet mediaUSENIX WOOT Conference on Offensive Technologies tweet media
English
1
2
13
668
Stijn Volckaert retweetledi
Meredith Whittaker
Meredith Whittaker@mer__edith·
📣Official statement: the new EU chat controls proposal for mass scanning is the same old surveillance with new branding. Whether you call it a backdoor, a front door, or “upload moderation” it undermines encryption & creates significant vulnerabilities signal.org/blog/pdfs/uplo…
Meredith Whittaker tweet media
English
201
3.8K
8K
2M
Stijn Volckaert retweetledi
stefan brunthaler
stefan brunthaler@stbrunthaler·
Woke up this morning and, about ten minutes in, got a paper acceptance notification. Excited to talk about it, but will have to wait until the next DL is over. In utmost brevity: We're using DRAM Rowhammer PUFs with software diversity to prevent reverse engineering. 🎉
English
1
5
14
5.1K
Mathias Payer
Mathias Payer@gannimo·
As always, Herbert's @NDSSSymposium #NDSSSymposium2024 keynote blew my mind. Looking at missed opportunities of interactions between hackers and academics, Herbert @vu5ec gave us a whirlwind tour of memory corruption and possible mitigations.
Mathias Payer tweet mediaMathias Payer tweet media
English
5
9
74
19.4K