-
Notifications
You must be signed in to change notification settings - Fork 0
/
cards.txt
36 lines (35 loc) · 1.32 KB
/
cards.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
Ignore access control
Use only a terminal (or: do not use the terminal)
Rewrite the tests without looking
Explain the whole system to a child
You learn only one secret. What's next?
You have one million dollars but you can only attack one function
What if you could force the function to execute twice?
You have full access for only 60 seconds. What do you do?
Start by reading the git history
How could an old bug come back?
Find the code that the developer hates the most
Delete a random file. What depends on it?
Write your ideas by hand. Limit yourself to one sheet of paper
What if all input was sent in reverse?
First, read the documentation of the dependencies
Assume the math is wrong
Slowly, then all at once
What if it was done your way?
Write the proof-of-concept before finding the exploit
Stop at once. Sleep on it
Go offline
Where is the best place to hide?
Use unacceptable numbers
Change the encoding
How could corruption impact reliability? How could unreliability cause corruption?
The developer lets you change 20 lines of code
What if you knew you couldn't be caught?
The dependencies are broken
One window, one tab, one screen
Do the comments tell the whole story?
The innocent TODO is a critical
Articulate hidden cycles
How can the state machine move backward?
Reverse the flow
By any means necessary, try all combinations