Use standard openssl tool for Premium Paywall challenge
See original GitHub issueThe Premium Paywall
challenge currently uses a third party web service to encrypt/decrypt the flag.
I suggest to use standard openssl instead. This way, users can better understand what algorithm including the mode of operation is actually used, without relying on the third party web service.
I will start working on a PR.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Use standard openssl tool for Premium Paywall challenge #419
This allows to get reproducible cipher texts with repeating encryption runs · There are no clues in the JuiceShop yet that point to...
Read more >bkimminich/juice-shop - Gitter
:wave: is the premium paywall challenge currently broken? no luck so far ... in a PR that uses a more standard tool (i.e....
Read more >Challenge solutions - Pwning OWASP Juice Shop
Use the bonus payload in the DOM XSS challenge. Solve the Perform a DOM XSS attack challenge; Turn on your computer's speakers! Paste...
Read more >security _check.docx - 1 Task 4 Unlock Premium Challenge to...
This is a cipher text that came out of an AES-encryption using AES256 in ... 6Task 4Premium Paywall: unblock Premium Challenge to access...
Read more >Pwning OWASP Juice Shop - GRIET SDC
description: 'O-Saft is an easy to use tool to show information about SSL ... Premium. Paywall. Unlock Premium Challenge to access exclusive content....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
On the other hand, exposing the IV along with the key is bad practice enough, I suppose… 😉
So, @ingben, feel free to send that PR! One idea for that one: Maybe instead of making it trivial with the current
you could do it slightly more obscured, like
{iv}.{key}
or{iv}#{key}
, so the file containsor
@irbian: You mean from the original challenge? The PHP source code on the page mentions it.