Hey Hackers of this spoopy month! 👻
Welcome to the Ciphey repo(s)!
This issue requires you to add a decoder.

This wiki section walks you through EVERYTHING you need to know, and we've added some more links at the bottom of this issue to detail more about the decoder.
https://github.com/Ciphey/Ciphey/wiki#adding-your-own-crackers--decoders

https://www.dcode.fr/t9-cipher
https://en.wikipe

This is more of a question with a potential follow-up suggestion: in the genre column, we do have drama/thriller and thriller/drama

Is there a valid reason behind this? If not, I would suggest making it more consistent (eg: pick one between the two and use it consistently across the list), so that sorting it properly groups them.

Also: since we do have categories already, why the column

App Attest allows your app to attach a hardware-backed assertion as a part of the request. Your server can use assertion to verify the request came from your genuine app, on a genuine Apple device.

https://developer.apple.com/videos/play/wwdc2021/10244/

https://developer.apple.com/documentation/devicecheck/assessing_fraud_risk

https://developer.apple.com/documentation/bundleresources/entit

A common protocol structure is to have a header containing a length field, followed by data of length bytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.

I do not know the best way to address this, but quick and easy way to support

It has been a pleasure for me to contribute to all of you 2 versions of this tool.

I've been working on other open source projects that I'm about to release for you, so I haven't finished trape version 3.0.

But, I invite you and the entire community that has used this project, to collaborate with some lines of code, implementing your own ideas and improving trape, turning it into a project o

🐛 Bug report

Description

Hacking Instructor doesn't take into account a custom domain.

Here's a part of my custom config:

application:
  domain: "example.com"

Take the "Login Jim" challenge instructor script. At the stage of inputting Jim's email, the instructor script expects "jim@juice-sh.op" and not "jim@example.com".

Looking at the source code, looks li

RustScan has an accessible mode, rustscan --accessible which should promise not to have any weird ASCII text in it.

Write CI that runs RustScan with --accessible a few times, with different flags / options and check the terminal output to see if it contains one of these:

1. [!]
2. [~]
3. [>]
4. | {}

If any of these characters appear in any of the tests, fail the CI. E

$ poetry run pywhat "b8cedc00407a4c56a3bda1ed605c6fc1"
Matched on: b8cedc00407a4c56a3bda1ed605c6fc1
Name: Datadog API Key
Exploit: Use the command below to verify that the API key is valid:
  $ curl -X GET https://api.datadoghq.com/api/v1/validate -H "Content-Type: application/json" -H "DD-API-KEY:
b8cedc00407a4c56a3bda1ed605c6fc1"

It's too broad and matches on any 32 character hex