←back to thread

449 points bertman | 2 comments | | HN request time: 0s | source
Show context
garblegarble ◴[] No.29703013[source]
The repo readme is pretty telling - this is being leaked to force this particular key to be blacklisted, I guess one group annoyed with others and wanting to cut off their access (and presumably the leaking group already has other L1 keys so doesn't fear this key being burned...)
replies(3): >>29703084 #>>29703220 #>>29704610 #
tyingq ◴[] No.29704610[source]
I also noticed it provides part of the functionality with a .pyc file, without including the normal python source. This one, for example: https://github.com/widevinedump/WV-AMZN-4K-RIPPER/blob/main/...

I'd be a little leery of running that outside of a sandbox.

replies(2): >>29721739 #>>29721821 #
masterofpupp3ts ◴[] No.29721739[source]
Forgive me for my ignorance, but would you mind explaining why providing functionality with a .pyc is potentially a red flag? I'm interested in learning more about Python codebases.
replies(1): >>29721775 #
1. tomc1985 ◴[] No.29721775[source]
.pyc files are the compiled bytecode for its corresponding .py file. It's scrambled, you would need a decompiler to inspect the source code and it would be very hard to read (compared to the original source).

People typically ship .pyc files when they want to hide what they are doing, for a wide variety of reasons.

replies(1): >>29722078 #
2. masterofpupp3ts ◴[] No.29722078[source]
Oh! That makes complete sense. I didn't know .pyc was the bytecode of a Python file. Thank you!