Please feel free to subscribe to the newsletter where I will announce when it's available :) https://kerkour.com/subscribe
1,277 karma · joined April 18, 2020
Please feel free to subscribe to the newsletter where I will announce when it's available :) https://kerkour.com/subscribe
That being said I'm sure that rustaceans disagree about the "No Silver Bullet" part (when you can compile to WebAssembly, write HTTP / TCP servers, embedded development and much more).
I believe that more than 100 books a month will be enough to make a comfortable living.
Today it makes no sense to reduce the price of the book because of the niche topic covered and my small audience, but for sure I will re-evaluate it later.
Yes, my ability to pay the rent is directly related to the number of books I sell.
That being said, I thought it was worth sharing because a lot of people think they can't make a living writing Open Source code. I hope to change their mind and give them ideas to take the leap.
Edit: rephrasing
Funding Open Source is a hot topic here and after more than one year of full-time work without being paid I have finally achieved (a little bit more than) ramen profitability.
I'm happy to answer any question.
In the book we will put ourselves in the shoes of attackers. From theory to practice, we will explore the arcane of offensive security and build our own offensive tools from scratch in Rust: scanners, phishing toolkit, shellcodes, advanced RAT...
Here is the accompanying GitHub repository: https://github.com/skerkour/black-hat-rust
Important: This is work in progress, feedback is welcome :)
In order to thank all the people who will help me make this book a reality by buying it in early access, I prepared a special bonus: a curated list of detailed analyses of the most advanced malwares of the past two decades. You will find inside great inspiration when developing your own offensive tools.
Edit: I Added a coupon for people hearing about the book here to save 10€: https://academy.kerkour.com/black-hat-rust?coupon=HACKERNEWS
In the book we will put ourselves in the shoes of attackers. From theory to practice, we will explore the arcane of offensive security and build our own offensive tools from scratch in Rust: scanners, phishing toolkit, shellcodes, advanced RAT...
Here is the accompanying GitHub repository: https://github.com/skerkour/black-hat-rust
Important: This is work in progress, feedback is welcome :)
In order to thank all the people who will help me make this book a reality by buying it in early access, I prepared a special bonus: a curated list of detailed analyses of the most advanced malwares of the past two decades. You will find inside great inspiration when developing your own offensive tools.
Edit: I Added a coupon for people hearing about the book here to save 10€: https://academy.kerkour.com/black-hat-rust?coupon=HACKERNEWS
Remote: Yes (exclusively)
Technologies: Go, Rust, VueJS, Typescript, VueJS
GitHub: https://github.com/skerkour
Blog: https://kerkour.com
Résumé/CV: Upon request
Email: sylvain.kerkour at gmail.com
----------------------------
After an attempt to launch my startup, I'm now looking for new technical challenges and to help make other people's lives better at the same time.
In the past years I have designed and implemented a Machine Learning service (automatic product recognition), an end-to-end encrypted app, a security automation platform and APIs / Single page apps.
I love open source and manage a moderately successful newsletter about it: https://kerkour.com
----------------------------
How can I help you?
Also I don't use monotonic generators, because in pratice, in my applications, it never make business sense to sort entities with a greater granularity than a millisecond, so even if I generate 10 entities' IDs in a millisecond, I will let the random part randomly sort the entities generated during this millisecond.
Monotonic generators, are in my opinion only useful when you require absolute ordering, like with events, and thus rarely are a concern.
I just find instagram's ID complex (custom epoch, mandatory use of RETURNING) while Ulid is elegant (easy to generate and use).
For me the biggest selling point was the interoperability with other kinds of UIDs, if later your requirements change.
Also, note that (at least in Rust) Ulid are implemented as u128, so are pretty fast.
* they are sortable so pagination is fast and easy.
* they can be represented as UUID in database (at least in Postgres).
* they are kind of serial, so insertion into indexes is rather good, as opposed to completely random UUIDs.
* 48 bits timestamp gives enough space for the next 9000 years.
Other than that, they have 80 bits of randomness, enough to be unique even if millions are generated per second.
It's far easier to convince a young person without a family nor passion in life to work for 12 hours a day for little money rather than experienced people.
It's also far easier to sell hyped, useless technological solutions to young, non-experienced people who don't understand the problem to solve.
I say this as a young developer who took too much time to recover from the marketing hype maintained by money seeking vendors.
In my opinion the best article about it is: https://blog.trailofbits.com/2019/08/06/better-encrypted-gro...
Instead of aiming the moon today, I may suggest to focus on only one thing and do it very well now.
My suggestion is to target mobile / desktop (convergent) linux. The story today is not good, and you seems to have achieved some interesting things with your UI shell that may take years to achieve with the usual linux technologies: Gnome or KDE.
You may even be able to quickly make a business by selling pre-flashed linux devices like raspberry pis, pinephones, pinebooks... with your beautiful and easy to use UI.