-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USMs created with WannaCRI cannot be opened by official SDK #12
Comments
It does not come with usm-break, the tool that encrypts the USMs, but I do know someone with access to that tool (they cannot share it as of now) and they have offered to supply USMs encrypted with the official encryption, if that's something you'd want |
Hi, thanks for reporting the issue. I'm still thinking if I should look at the SDK. So for now let me ask you some questions. Can you give more information about how you made the usm that was incompatible with viewer? Did you use vp9 or h264? Encrypted or not? Are there any helpful errors that the viewer showed? |
I tried unencrypted and encrypted h264 at least, the error was "Unexpected end of file" if my memory serves me |
Thanks for the info I think I know the problem. I'll try to investigate on the weekend. As for your friend who has access to the official tool that encrypts usms. Can you ask them to produce both encrypted and non-encrypted versions of h264, vp9, and other codecs supported by usm. Same goes for usms with audio. I'm also interested in how usm encrypts other media types such as alpha channels, my hunch is that it's the same as normal videos. I'd greatly appreciate if you and your friend can produce and share those videos so I can analyze them. There are also other usm stuff like subtitles that I'm not sure how it's stored. If those are not in the sdk above, can you and your friend assist on those too? Thanks again! |
Of course!! I'll get right on that |
These all have subtitles and alpha channels, so that should help! The .enc files are literally just the encrypted .usms. |
Also the encryption key is 9923540143823782 or 0x002341683D2FDBA6 in bytes |
Thanks, I'll take a look at these. Apologies for the delay |
Hey, any update on this? Just curious! |
https://cdn.discordapp.com/attachments/879231833366204429/1185599541408440410/CRI_Sofdec2_Tools_Manual.7z |
Using the official SDK found here, https://archive.org/details/new-criware-sdk you can't open the usms generated with WannaCRI in the USM viewer included in the SDK, might be an interesting thing to investigate.
You can also create official USMs with this tool, which could be useful for reverse engineering purposes.
The text was updated successfully, but these errors were encountered: