{
  "type": "edit",
  "branch": "%IaEHdwQKt1aBo8iwaq37JxoMjrp+Z0aNzu12vugksCg=.sha256",
  "root": "%I6FaCzdXcKAiZp0LVhwVluDeDkhNPGQXEqNEkUFLq34=.sha256",
  "updated": "%IaEHdwQKt1aBo8iwaq37JxoMjrp+Z0aNzu12vugksCg=.sha256",
  "original": "%IaEHdwQKt1aBo8iwaq37JxoMjrp+Z0aNzu12vugksCg=.sha256",
  "text": "Ok, so I haven't fixed this yet, mostly because of my lack of familiarity with the `secure-scuttlebutt` module.\n\nI should also note that I'm using a fork of scuttlebot from lts, so I'm not exactly using the latest ssb either. The connections layer doesn't work for me, so I can't use the last three major versions of ssb over here. \n\nI tried just commenting out the `unboxer` stuff, and that didn't work because errors started throwing in all kinds of flume modules that I have no control over.\n\nMy first step has been getting more familiar with how `secure-scuttlebutt` works, and how it has changed over time. In the process I did discover when this vulnerability was introduced:\n\n![2019-02-25-162602_1004x109_scrot.png](&gVqUDqFe55vQzk9p2j1dqxQtgQXqb6wS46fK9l2Ao5s=.sha256)",
  "mentions": [
    {
      "link": "&gVqUDqFe55vQzk9p2j1dqxQtgQXqb6wS46fK9l2Ao5s=.sha256",
      "name": "2019-02-25-162602_1004x109_scrot.png"
    }
  ]
}