Big fan of the idea of offline in-browser tools: works on any device, and "installing" the program is as simple as visiting a webpage or opening the saved HTML file. This one uses WebAssembly, but even that isn't necessary: I wrote a couple of PDF tools for my own use that simply use pdf-lib: https://shreevatsa.net/pdf-pages/ https://shreevatsa.net/pdf-unspread/
I created something similar for pdf diffing since I needed “visual” diffing instead of “textual” diffing. It uses Mozilla’s PDF.js library as the rendering engine. It’s amazing how much you can do in-browser. https://parepdf.com/
PDF Tool – Modify PDFs in the browser without uploading
191–198 of 198 posts
Re: PDF Tool – Modify PDFs in the browser without uploading
#192Earlier quoted context omitted.
Your links point to people and services using intercepting proxies , not configuring one in their browsers. Techniques intercepting TCP traffic and redirecting it to a proxy will not work when the traffic is UDP. This is not a browser issue. In this thread we were talking about the user willingly configuring a proxy in the browser or OS.
> Your links point to people and services using intercepting proxies, not configuring one in their browsers. Sorry, I didn't look too closely through any of those links, because I never used those specific products myself. But I do clearly remember this being an issue for me back in the day. So I dug further. You'll be happy to see this bug report[1] and this commit[2]. Note these words from a Chromium dev: "This cod…
Re: PDF Tool – Modify PDFs in the browser without uploading
#193Earlier quoted context omitted.
Your links point to people and services using intercepting proxies , not configuring one in their browsers. Techniques intercepting TCP traffic and redirecting it to a proxy will not work when the traffic is UDP. This is not a browser issue. In this thread we were talking about the user willingly configuring a proxy in the browser or OS.
> Your links point to people and services using intercepting proxies, not configuring one in their browsers. Sorry, I didn't look too closely through any of those links, because I never used those specific products myself. But I do clearly remember this being an issue for me back in the day. So I dug further. You'll be happy to see this bug report[1] and this commit[2]. Note these words from a Chromium dev: "This cod…
Re: PDF Tool – Modify PDFs in the browser without uploading
#194Earlier quoted context omitted.
> Your links point to people and services using intercepting proxies, not configuring one in their browsers. Sorry, I didn't look too closely through any of those links, because I never used those specific products myself. But I do clearly remember this being an issue for me back in the day. So I dug further. You'll be happy to see this bug report[1] and this commit[2]. Note these words from a Chromium dev: "This cod…
Thanks! This is scary, however you'll agree that a bug on Chrome closed 6 years ago is a far cry from your claim that "HTTP and SOCKS proxies cannot carry QUIC traffic, so browsers don't even try. They just send it right through" present tense . Still thank you for finding this reference, it is a sign that setting a proxy in your system is not as secure as a firewall/netns.
Yeah, I agree. I should've checked the validity before posting it, instead of just going by memory from years ago.
> ... finding this reference ...
It was a lot more effort than I'd have liked to put into my original comment, but hey, I was ticked off by your accusation of spreading FUD. Also didn't help that search engines today aren't what they used to be.
Re: PDF Tool – Modify PDFs in the browser without uploading
#195[dead]
Re: PDF Tool – Modify PDFs in the browser without uploading
#196Big fan of offline tools. I have a small collection of tools at https://www.webutils.app/ and have been meaning to add pdf tools for a while.
Re: PDF Tool – Modify PDFs in the browser without uploading
#197Earlier quoted context omitted.
What does it even mean lol. I really like how you implied that it's a problem of WebAssembly. How is checking a web page's network connection, WebAssembly or not, harder than reading ALL the source code (if you don't read them all you can't be sure!) of a non-trivial app?
I was expecting something along the lines of pdf.js or something. WebAssembly was a shock, but I looked at the asm, saw golang, decompiled back to go and looked. all good. still... all it takes is an errant http.client call.