![iFixit Tears Down New M4 MacBook Air [Video]](https://www.iclarified.com/images/news/96717/96717/96717-640.jpg)
![Apple Officially Announces Return of 'Ted Lasso' for Fourth Season [Video]](https://www.iclarified.com/images/news/96710/96710/96710-640.jpg)
![9to5Rewards: Last chance to win a MacBook Pro from Chargeasap [Giveaway]](https://i0.wp.com/9to5mac.com/wp-content/uploads/sites/6/2024/10/M4-MacBook-Pro-doesnt-tempt-me-because-Apple-Silicon-Macs-are-almost-too-good.jpg?resize=1200%2C628&quality=82&strip=all&ssl=1)
![[The AI Show Episode 139]: The Government Knows AGI Is Coming, Superintelligence Strategy, OpenAI’s $20,000 Per Month Agents & Top 100 Gen AI Apps](https://www.marketingaiinstitute.com/hubfs/ep%20139%20cover-2.png)
![[The AI Show Episode 138]: Introducing GPT-4.5, Claude 3.7 Sonnet, Alexa+, Deep Research Now in ChatGPT Plus & How AI Is Disrupting Writing](https://www.marketingaiinstitute.com/hubfs/ep%20138%20cover.png)
![How to become a self-taught developer while supporting a family [Podcast #164]](https://cdn.hashnode.com/res/hashnode/image/upload/v1741989957776/7e938ad4-f691-4c9e-8c6b-dc26da7767e1.png?#)
![If I use an API licensed with apache 2.0 in my project, what license do I use and what should I be aware of? [closed]](https://cdn.sstatic.net/Sites/softwareengineering/Img/apple-touch-icon@2.png?v=1ef7363febba)
.jpg?#)
.jpg?#)
Recon v2: Um curto update sobre como estou mudando meu processo de recon
Tradicionalmente, sempre segui um processo recon simples e básico, focado em subfinder + httpx + nuclei + ffuf (antes usava amass, mas como gosto do projectdiscovery, resolvi migrar pro subfinder). Porém, acompanhando esse caso da DeepSeek, fiquei pensativo porque meu recon simplesmente não pegaria esse banco de dados aberto (estava aberto em http://oauth2callback.deeopseek.com:8123), porque só faço enumeração passiva de subdomínios com o subfinder só probo as portas 80 e 443 com o httpx Por isso, resolvi testar as dicas da thread e dar um up no meu recon. // Detect dark theme var iframe = document.getElementById('tweet-1884720268150468825-340'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1884720268150468825&theme=dark" }
Tradicionalmente, sempre segui um processo recon simples e básico, focado em subfinder + httpx + nuclei + ffuf (antes usava amass, mas como gosto do projectdiscovery, resolvi migrar pro subfinder).
Porém, acompanhando esse caso da DeepSeek, fiquei pensativo porque meu recon simplesmente não pegaria esse banco de dados aberto (estava aberto em http://oauth2callback.deeopseek.com:8123), porque
- só faço enumeração passiva de subdomínios com o subfinder
- só probo as portas 80 e 443 com o httpx
Por isso, resolvi testar as dicas da thread e dar um up no meu recon.
// Detect dark theme var iframe = document.getElementById('tweet-1884720268150468825-340'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1884720268150468825&theme=dark" }
