add Ride Closed section to lookup.md, strikethrough and notate dead link to lookup.milksad.info

This commit is contained in:
Dustin Johnson 2023-11-13 23:11:33 -05:00 committed by Christian Reitter
parent b18e42a4dd
commit 96f1d0db76
1 changed files with 25 additions and 2 deletions

View File

@ -4,6 +4,29 @@ layout: home
permalink: /lookup.html
---
# Ride Closed 🚧
Dear users,
The Milk Sad vulnerability Lookup Service was offered for 90 days by the Milk Sad team upon disclosure as a free service to help users determine if their wallets were impacted by the Milk Sad vulnerability.
This service has been taken down permanently and with prejudice.
Understandably, we cannot keep the service running forever. While there were significant cost considerations in running this service in the first place, we felt it was the right thing to do.
[The code for the lookup service](https://git.distrust.co/milksad/lookup) will remain open and available to all for as long as we can reasonably do that.
Best regards,
Milk Sad team
-----
-----
# _Original Page Content is Below:_
# (FOR HISTORICAL REFERENCE ONLY)
-----
-----
# Lookup service
To help people identify if they are impacted by Milksad, we are providing a web service to check if your mnemonic is in the vulnerable set. Note that this service -only- covers mnemonics impacted by Libbitcoin Explorer (`bx`) versions `3.0.0` to `3.6.0`, though it may be updated over time to cover other related vulnerabilities we are researching.
@ -40,7 +63,7 @@ For those wishing to limit metadata sent to us or our server provider, we encour
* Option 1: Browser
Visit [https://lookup.milksad.info](https://lookup.milksad.info) and paste your sha256 hash
Visit (DEAD LINK:) ~~[https://lookup.milksad.info](https://lookup.milksad.info)~~ and paste your sha256 hash
* Option 2: Terminal
@ -48,4 +71,4 @@ For those wishing to limit metadata sent to us or our server provider, we encour
curl https://lookup.milksad.info/check?sha256=a7278e802055b3d17a66afe498428ac70c828ad69f25d02254c3b76b08d8cf8a
```
3. Inspect the response for ```vulnerable``` or ```no match```
3. Inspect the response for ```vulnerable``` or ```no match```