Paper “Ouroboros: A Provably Secure Proof-of-Stake Blockchain Protocol”
https://eprint.iacr.org/2016/889.pdf
- to generate a single block of bitcoin > 2^60 hash operations (energy requirements ~ small country)
- -> change “proof of work” to something more efficient with similar guarantees
- Proof of Work : choose randomly the miner to issue the next block -> depends on computational power
- Proof of Stake (PoS) : choose randomly proportionally to the stake.
- PoS design challenge: simulate leader election process (fair randomized election)
- Result:
- Ouroboros, provably secure PoS system. First blockchain protocol with rigorous security analysis
-
- Model that focus on persistence and liveness
- Persistence: 1 node claim the transaction as “stable”, the remaining nodes, if queried and responding honestly, will also report it as stable
- Liveness: once an honestly generated transaction has been made available for a sufficient amount of time (“u” time steps), it will become stable.
- Stability - predicate parameterized by “security parameter” k, that will affect the certainty (e.g. “more than k blocks deep”).
- Liveness + persistence = robust transaction ledger
-
- Novel blockchain protocol, based on PoS. Protocol assumes that
-
- Set of formal arguments establishing that no adversary can break persistence and liveness. Assumptions:
- Network is synchronous (upper bound of communication time)
- Number of stakeholders is available as needed to participate in each epoch
- Stakeholders do not remain offline for long periods of time
- Adaptivity of corruptions is subject to a small delay (measured in rounds linear in the “security parameter”)
- Distinguish “covert attack” (тайная атака) class of general forking attacks. Adversary wishes to break the protocol, but prefer not to be caught
-
- Present a novel reward mechanism for incentivizing the participants to the system which we prove to be an approximate Nash equiilibrium (ни один участник не может увеличить выигрыш, изменив свою стратегию, если другие участники своих стратегий не меняют).
- Attacks like “block withholding” and “selfish-mining” are mitigated by the design
- Core idea: provide positive payoff for those protocol actions that cannot be stifled by a coalition of parties that diverges from the protocol.
Платить за те операции, которые сложно подавить коалицией. Если эти операции просто сделать, то мы сохраним равновесие Нэша
-
- Stake delegation mechanism, for large number of stakeholders (delegate their “voting rights”)
- Model, protocol -> проверить, как атаки будут работать в их системе. ПРоверили:
- double spending attacks,
- transaction denial attacks
- 51% attacks,
- nothing-at-stake
- desynchronization attack
- others.
- Benchmark + analysis of processing performance (5-10-100 times faster)
- 56 страниц
The Absurdly Underestimated Dangers of CSV Injection
http://georgemauer.net/2017/10/07/csv-injection.html
- Old news
- Imagine a time or ticket tracking app: Users enter their time/tickets, but can’t see data of other users. Site admin exports entries to a csv, open in a spreadsheet app.
- CSV RFC states: “csv files contain passive text data that should not pose any risks”
- Attack Vector1: “=2+5”. Export to Excel, Google Sheets execute the code to “7”
- “=5+2+cmd |’ /C calc ‘!A0 -> run calculator on Windows. Admin rights, run any code.
- Attack Vector2:
IMPORTXML
command to send data anywhere
- Send data not only this Google Sheets, but from anywhere, any other table that it can
read
. Need “SheetID”, but it is part of URL, often shared. Work in Excel!
- Prevention: “tab” before any formula sign (=,-,+,@). May be inside of the quotes.
How Google and Microsoft made email unreliable
http://penguindreams.org/blog/how-google-and-microsoft-made-email-unreliable/
- Privacy, email-server, Google + FBI
- Google (G+), Facebook (messenger) and closed communication: No XMPP already
- Overaggressive Spam Filters:
- separate email server -> spam
- pdf is attached -> spam
- ip в подозрительной сети - spam
- Facebook messenger: fee to reach people (Цукерберг: $100)
- 2009: social networking is more often, then email