Specify deposit amount to deposit and get invoice.
I was surprised to see the data ... and this is someone else's.
And the next thing you did was to search for wallet.dat. right?
PoC||GTFO=("proof of concept or get the fuck out") is another huge collection of awesome hacker/computer stuff.
I'd compare it to Paged Out! (btw, issue 3 comes soon!). Actually I'd compare Paged Out! to PoC||GTFO because it's older.
As with many good books, I haven't read it completely (yet?). But I am sure you'll find at least 1 in this huge pack of articles.
Maybe it's "ELFs are Dorky, Elves are Cool"?
( ) ( )
)\ ) ( /( ( ( * ) )\ ) ( /(
(()/( )\()) )\ )\ ) ` ) /((()/( )\())
/(_))((_)\ (((_) (()/( ( )(_))/(_))((_)\
(_)) ((_) )\___ _ _ /(_))_ (_(_())(_))_| ((_)
| _ \ / _ \((/ __|| || |(_)) __||_ _|| |_ / _ \
| _/ | (_) || (__ | || | | (_ | | | | __| | (_) |
|_| \___/ \___|| || | \___| |_| |_| \___/
|_||_|
Wow, very interesting. I'm more interested in how someone comes up with such ideas.
The crazy test cases often get generated by computers. For example this pseudo program could have found a bug like in the video:
- generate a url
- let parser 1 decide whats the host in that url
- let parser 2 decide whats the host in that url
- if they don't agree, print url (one of both parsers is wrong!)
- go to beginning
Ofc I'm leaving out a lot of things here, but that is the rough approach I'd use to find bugs like this.
If you're interested read the fuzzing book, I've linked it and other resources about fuzzing here.
DEF CON talk: https://www.youtube.com/watch?v=iFS25HfTe20
The fuzzing book is a great resource! Here's a one-liner that I found useful for globbing wordlists together to test out some of the concepts there
fuzz = np.array(list(reduce(np.append, map(lambda f: np.genfromtxt(f, delimiter='\n', dtype=str), list(w.absolute() for w in pathlib.Path('wordlists').glob('**/*fuzz*'))))))I'd also like to add that fuzzing isn't just about security. It is mostly used there, but letting computers find the bugs is useful for everyone.
Interesting video, but I've been halfway through understanding it :D
Interesting concept! I also like that you use PGP. It's one of the features I want to add to ZapRead - that you can use PGP to encrypt private messages and sign posts!
Awesome idea, will look at the page later! I'd like a more detailed post in the Privacy group ;)
Buy a nano s, save that seed somewhere safe, if you are going to keep a virtual copy, put it on word with a password, later into a rar protected by a different password, put those files in a encrypted usb with yet another password.
If you are going to upload files to your Google drive or OneDrive, make sure you use different passwords than your email and put 2fa in your email.
Email protected by strong password plus 2fa.
To make sure no employee of Google or Microsoft can steal your files, put strong password on a word file, put that file in a encrypted file folder encrypted by rar. And if you can put those files into another encryption tool, so that attackers need to bypass at least 3 strong different passwords.
Once you do that don't open those files until is need it and remember all of your password because if one is lost the whole thing is lost.
Example of strong password
[email protected]&&&///
Don't use your name, or your family, or girlfriend name. Don't use something obvious that way even if you upload your files to a cloud your seed will be protected and make sure it is protected by at least 3 different passwords like that or stronger.
Don't write down your password. You must remember them only in your head.
Best way will be to write down in your brain only the 12 or 24 seed. But that's hard. I have been doing that, and it is not easy.
The most secure way will be to know your 12 or 24 words only in your head as a memory, but you must remember it and make sure by creating the wallet, memorized it and after a while check if you still can remember it like 6 months later, if you can still remember your seed after one year than you can move funds to it. But you must keep on remember it every month because memory in head is very hard.