kodbraker

8 ms·

1. 1.▲
   by kodbraker 5mo ago

   For my case, it was almost certain. As it happened single day, the card i use was a virtual card only used in couple big ecommerce websites etc. If it was leaked somewhere else, i think they wouldn't bother logging in some unrelated ac
2. 2.▲
   by kodbraker 5mo ago

   The rate they try becomes very non frequent when they use multiple card validation apis. I'm not sure how it can be related when it's different pan numbers, different source ips etc. Enumerating CVC2 with a single PAN is a differe
3. 3.▲
   by kodbraker 5mo ago

   I agree with the seperate card. That was my seperate card and luckily the amount was not quite big because of that. >Weak point was a password that lead to another merchant not using 3D secure Well leaking a password shouldn't cause
4. 4.▲
   Credit cards are vulnerable to brute force kind attacks(metin.nextc.org)

   241 points by kodbraker 5mo ago|192 comments
5. 5.▲
   High Performance Geoip Blocking in eBPF with XDP(metin.nextc.org)

   5 points by kodbraker 4y ago|1 comments
6. 6.▲
   by kodbraker 4y ago

   hey, great work. I couldn't find the specifics of the benchmark. Is there, by any chance you compare 1 instance of single threaded redis running on 64vcore to a multithreaded key-value store? Can we see such disparity in benchmark even
7. 7.▲
   Deep Dive into Hello World in Java(medium.com)

   2 points by kodbraker 5y ago|0 comments
8. 8.▲
   by kodbraker 6y ago

   What's the blogging engine? Looks familiar