Open lol98lol98x opened 6 months ago
danieltyukov
commented
6 months ago Well, they arent blurring the images, they are just fetching a low res png image from their server and scaling to look blurred, it's just a big low-resolution picture. I am looking into it.
You can star the repo and check in once in a while or also do pull requests for suggestions.
lol98lol98x
commented
6 months ago I noticed it was a tiny image too, after playing with the html. Any ideas on what can be done to resolve this? There has to be an original image we can find and load somehow. However it may be dynamic and difficult to do. As I think they're using a self hosted and outside CDN for things now. They are doing this to attempt to fix these bypass methods.
teahcerzpet
commented
6 months ago Hey @danieltyukov or @lol98lol98x any chance you guys have thought of a fix for this? Praying you do somehow :(
capellavacancies
commented
6 months ago Hello, I installed 2.3.0 on edge/mac and still get blurred pages.
Thanks
L30-stack
commented
6 months ago Hey @danieltyukov, dont know if you ralized yet, but fetching the low res images p. ex.: "page3.webp" as the file "bg3.png" will return you the full res image from the server without checking any authentification ;)
Im currently still having my finals but would love to help you implement a workaround!
lol98lol98x
commented
6 months ago @L30-stack > Hey @danieltyukov, dont know if you ralized yet, but fetching the low res images p. ex.: "page3.webp" as the file "bg3.png" will return you the full res image from the server without checking any authentification ;)
Im currently still having my finals but would love to help you implement a workaround!
Show me an example link vs what it should be. And I'll try to automate it via javascript
Because when I try what you said I get this.
NoSuchKey
danieltyukov
commented
6 months ago Hey @danieltyukov, dont know if you ralized yet, but fetching the low res images p. ex.: "page3.webp" as the file "bg3.png" will return you the full res image from the server without checking any authentification ;)
Im currently still having my finals but would love to help you implement a workaround!
really cool man, if you can either make a pr or drop me some instructions on how you achieve that ill make a release under your name for this repo.
L30-stack
commented
6 months ago @L30-stack > Hey @danieltyukov, dont know if you ralized yet, but fetching the low res images p. ex.: "page3.webp" as the file "bg3.png" will return you the full res image from the server without checking any authentification ;)
Im currently still having my finals but would love to help you implement a workaround!
Show me an example link vs what it should be. And I'll try to automate it via javascript
Because when I try what you said I get this.
NoSuchKeyThe specified key does not exist.
But I'm giving it a try rn.
o0LINNY0o
commented
6 months ago For a noob ,,, how to you fetch the *.png instead .
Right Clicking and saving isnt working
L30-stack
commented
6 months ago @o0LINNY0o in the newest commit the png should be fetched automatically and is added to the created print-preview. If there occur any issues let me know :)
o0LINNY0o
commented
6 months ago @o0LINNY0o in the newest release the png should be fetched automatically and is added to the created print-preview. If there occur any issues let me know :)
i downloaded and install the source and the 2.3.0 and i still get this :
EDIT: 2.3.0 also gives m,e this error:
downloadBtn.innerHTML = 'Download'; downloadBtn.addEventListener('click', (event) => {
L30-stack
commented
6 months ago There is no release for the current changes yet. Please download the code manually.
Furthermore could you please add a fullscreen screenshot and the full error message.
o0LINNY0o
commented
6 months ago Sure thing & thanks for your support.
Here is the 2.3.0 Error https://imgur.com/a/oxRUf1C
EDIT: Just realised the previous post cut away alot of it. But if i edit it , its still there ???
the Manually Downloaded Code was creating a clear download , but the pages were made up of the previous clear picture...
eg. Page 2 was repeated for a blurred out Page 3
danieltyukov
commented
5 months ago @L30-stack @o0LINNY0o https://github.com/danieltyukov/studocuhack/releases/tag/v2.4.0
latest release has the changes fixing the error + L30 changes, feedback is welcome, ill keep this issue open for now
danieltyukov
commented
5 months ago @L30-stack the blur page is still there, I am still checking over your added code, and your reference links, I think they added secure protection for those pages on the server side right?
L30-stack
commented
5 months ago Hey @o0LINNY0o,
I just tested your document. The issue you get is unfortunately currently not supported.
Studocu sometimes separates documents in a background (we support loading the full res image) and text in the front (currently not supported).
Therefore in your case the text from page 1 is displayed in all pages where the new background was added but no text was available. (Page 3,6,9...)
L30-stack
commented
5 months ago @L30-stack the blur page is still there, I am still checking over your added code, and your reference links, I think they added secure protection for those pages on the server side right?
The full res pages are only added to the pdf document view in the second window. Still works fine for me
tooxo
commented
1 month ago From the network logs, it looks like they implemented something similar to this: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-urls.html
I don't think this is possible to circumvent.
danieltyukov
commented
3 weeks ago @tooxo i am currently overall studying their method, this part you got right, here is some basic info you can then through reference dig deeper on bypassing that stuff too https://labs.detectify.com/writeups/bypassing-and-exploiting-bucket-upload-policies-and-signed-urls/
I am personally having issues with removing the blur myself. And I see your code also is.
Any thoughts or ideas on how to get around this? Or how it is chosen which pages will be blurred? I cant even manually figure out how to bypass the blur in dev tools.