## analysisWe get a binary and an full excution trace of one run of the binary. After analyzing the binary, we soon came to the conclusion, this is a handwritten RSA decryptiondoing C^D mod N (C is user input number). The intresting part here: for the modular power a [square and multiply](https://en.wikipedia.org/wiki/Exponentiation_by_squaring) algorithm is used. this algorithm is left shifting the bits of the userinput and if highest bit is one it will do modular multiplication, else nothing for calculating the RSA.
## insightso related to the fact we have an excution trace, we can look at the place in the code, where based on top most bit the decison is done, to do multiplication or not, and from that decision we can directly see the bitvalue, so all needed to do is to check every time the algo does that compare (highest bit 1 or 0) and record the bits.those bits converted to a decimal number will be our input to get the flag
```c...4013b6:       48 b8 00 00 00 00 00    movabs $0x8000000000000000,%rax4013c0:       48 39 c2                cmp    %rax,%rdx
4013c3:       75 40                   jne    401405 <main+0x1cf>        <------401405:       8b 85 b0 f9 ff ff       mov    -0x650(%rbp),%eax
40140b:       48 98                   cltq40140d:       48 8d 14 c5 00 00 00    lea    0x0(,%rax,8),%rdx...```
## doing it with grep and other linux command line tools :-)
- grep the tracefile for the "jne    401405 <main+0x1cf>" at 4013c3 and output the following line, so we know where the execution went (-A 1)- drop grep line separators with --no-group-separator- drop the 4013c3 lines from the jne- use awk printing 0 or 1 depending on next lines address- evaluate that expression and put it into bc for converting to base 10- avoid line breaks in bc with BC_LINE_LENGTH = 0
## solution:echo "obase=10; ibase=2; $(grep --no-group-separator -A 1 4013c3 trace | grep -v '4013c3' | awk '{if($1 == "401405:") printf "0"; else printf "1";}') " | BC_LINE_LENGTH=0 bc
results in:244652648608644057289603953074612700175933964244789320848667909167563692702652547784242339814218808951063055612658793570186844889979282952606878226608877859935559988556621623278752812292605612612163883997532869509885618332866441068962865470136130272926263303521750180711550883814600026677234330838029265221441047841355637850083056067511836089295432603059046109298537904428654107114553910703320935211803599935665225999452564664140186232164739291375407556107412707105250411308366447742913058979723684840765449422267902293487537073300912104264330520400754843332881465525532116517816288168335852096828051764240859454454009518120111671812902113201938369763608841769720763131720010223805776325980208111929662026610968279056747490265115993253416851071451892127738460444147514901971784385322720069737101076139227245987315223123169336706863690888801293487213146614146679028050257150777887496982927824949105219206894794372697828812226397922441686397417061966543488748591869285400239357533529688996471390996874988047597260063994210684092801510867133594884893681119353051040329814500624965262408435785310992711659906711739870502390260550767314380870394028475183756688989994399612240550769839124489086507436798682013488698499282429664122768579273
which gives us the flag, when input into challenge executable :-)
#### dam{and_1nto_d4ta_depend3ncy}
macz