all my friends are dead

any active sec bloggers? post 'em if ya got'um

here are some dead ones: http://www.devttys0.com/blog/ --(embeded devices hacking) --2016 https://spareclockcycles.org/ --(some interesting web and mobile exploits) --2012 http://thomascannon.net/ --(more mobile hacking) -- 2015

not my blog, but online friends blogs, https://thecyberviking.com/blog.html https://ragsec.co.uk/

I only know these digdeeper.neocities.org geneticabhorrence.neocities.org eldritchdata.neocities.org spyware.neocities.org rainheaven.neocities.org

>>9130 Pardon my ignorance and frogposting, but is opening a pdf like in > eldritchdata.neocities.org safe from a security perspective? Or is downloading them the main risk?

>>10271 Opening them, especially in adobe is asking for your box to be shepherded into somebodies botnet. Could learn how to manually inspect them if you really care enough. Format (mostly) is well documented and the compression formats are common enough. One could probably soykaf out something in python\whatever in an afternoon that can deal with everything inside but the postscript with little more than official documentation. https://www.adobe.com/devnet/pdf/pdf_reference.html https://www.adobe.com/devnet/pdf/pdf_reference_archive.html

https://latacora.micro.blog/

>>10272 I know there are pdf exploits for adobe reader. Never paid too much attention though cause i figured its software specific and nobody makes the effort targeting fringe linux readers. Am i wrong?

>>10272 pdf.js is how most people open PDFs now due to convenience. First the attacker needs to figure out how to exploit the PDF program to run code in the sandbox, then he needs to actually break out of the sandbox. For the latter there are processor exploits but those are still considered exotic and are architecture specific. Why do people freak out about PDF documents? They aren't more inherently dangerous than the hypertext documents you download from websites all the time, if anything they're harder to exploit now.

>>10282 >Why do people freak out about PDF documents recent new wave came with warnings issued, i guess its that.

>>10271 The pdfs are all safe. Mostly stuff pulled from other lain sec threads but you can always use a secure Firefox instance in a vm if you want to be sure.

>>10280 >>10282 >>10283 PDF-based exploits that don't rely on the reader executing arbitrary code are pretty exotic. However Acrobat Reader and NitroPDF both do this by default and are extensively used in corporate environments. (PDFs using Javascript are also widespread in corporate). Accordingly, corporate sec people talk about them a lot. If you have a reader that doesn't support JS you're fine. Similar problem to MS Office macros. If you turn them off, you don't have much to worry about, but some people need them for some business purpose. I know mupdf and the default GNOME PDF reader don't support scripts at all.

>>10272 >>10280 >>10282 >>10283 >>10302 >>10308 https://www.decalage.info/en/exefilter >Can detect, remove or disable active content in some formats: >PDF: JavaScript, Launch actions, Embedded files (effective against most current PDF malware, even zero-day exploits)

>>9026 https://thecyberviking.com/Rag_Around_The_World.html Scary soykaf

>>10344 >>10345 I try to take care to maintaining the pdfs integrity but I may convert then to html and make dedicated pages for each. But it will take me weeks or months to do so. Any tips to give them a more secure way to post them on EldritchData lain can recommend is appreciated.

https://krebsonsecurity.com/

>>10282 PDF.js is more secure than one may think. It's feature set is sorta limited compared to other readers - which is a plus because less attack surface. It also runs in a web browser - which is usually heavily sandboxed anyway.