A user is puzzled by how their subdomain, used for internal documentation and not linked anywhere publicly, was discovered and accessed by an external user. They're concerned about potential security vulnerabilities and are seeking explanations for how this could have happened, considering they haven't shared the subdomain's address. The user is ruling out DNS brute-forcing due to the subdomain's unique and unguessable name. They're particularly perplexed because the subdomain isn't indexed by search engines and hasn't been exposed through any known channels.
A Brown University undergraduate, Noah Golowich, disproved a long-standing conjecture in data science related to the "Kadison-Singer problem." This problem, with implications for signal processing and quantum mechanics, asked about the possibility of extending certain "frame" functions while preserving their key properties. A 2013 proof showed this was possible in specific high dimensions, leading to the conjecture it was true for all higher dimensions. Golowich, building on recent mathematical tools, demonstrated a counterexample, proving the conjecture false and surprising experts in the field. His work, conducted under the mentorship of Assaf Naor, highlights the potential of exploring seemingly settled mathematical areas.
Hacker News users discussed the implications of the undergraduate's discovery, with some focusing on the surprising nature of such a significant advancement coming from an undergraduate researcher. Others questioned the practicality of the new algorithm given its computational complexity, highlighting the trade-off between statistical accuracy and computational feasibility. Several commenters also delved into the technical details of the conjecture and its proof, expressing interest in the specific mathematical techniques employed. There was also discussion regarding the potential applications of the research within various fields and the broader implications for data science and machine learning. A few users questioned the phrasing and framing in the original Quanta Magazine article, finding it slightly sensationalized.
Discovery Coding is a software development approach prioritizing exploration and experimentation over rigid upfront planning. It emphasizes building small, functional prototypes to rapidly test ideas and gain a deeper understanding of the problem domain. This iterative process allows for continuous learning and adaptation, enabling developers to discover the best solutions organically, rather than being constrained by initial assumptions. The core principle is to treat coding as a tool for investigation, using it to uncover insights and refine the direction of the project as development progresses. This approach embraces uncertainty and recognizes that the best path forward often emerges through experimentation and discovery.
HN users generally praise the "discovery coding" approach described in the linked article. Several commenters share their own experiences with similar workflows, emphasizing the benefits of iterative exploration and experimentation for learning and problem-solving. Some highlight the importance of setting aside dedicated time for this type of coding, contrasting it with the pressure of deadline-driven work. Others suggest tools and techniques that can facilitate discovery coding, like using Jupyter notebooks or focusing on visual outputs. A few caution against over-reliance on this method for larger projects, advocating for more structured planning when necessary. There's also a discussion on how this relates to different learning styles and the potential downsides, such as getting lost in tangents or feeling unproductive.
Wikenigma is a collaborative encyclopedia cataloging the unknown and unexplained. It aims to be a comprehensive resource for unsolved mysteries, encompassing scientific enigmas, historical puzzles, paranormal phenomena, and strange occurrences. The project encourages contributions from anyone with knowledge or interest in these areas, with the goal of building a structured and accessible repository of information about the things we don't yet understand. Rather than offering solutions, Wikenigma focuses on clearly defining and documenting the mysteries themselves, providing context, evidence, and possible explanations while acknowledging the unknown aspects.
Hacker News users discussed Wikenigma with cautious curiosity. Some expressed interest in the concept of cataloging the unknown, viewing it as a valuable tool for research and sparking curiosity. Others were more skeptical, raising concerns about the practicality of defining and categorizing the unknown, and the potential for the project to become overly broad or filled with pseudoscience. Several commenters debated the philosophical implications of the endeavor, questioning what constitutes "unknown" and how to differentiate between genuine mysteries and simply unanswered questions. A few users suggested alternative approaches to organizing and exploring the unknown, such as focusing on specific domains or using a more structured framework. Overall, the reception was mixed, with some intrigued by the potential and others remaining unconvinced of its value.
Summary of Comments ( 188 )
https://news.ycombinator.com/item?id=43285725
The Hacker News comments discuss various ways a subdomain might be discovered, focusing on the likelihood of accidental discovery rather than malicious intent. Several commenters suggest DNS brute-forcing, where automated tools guess subdomains, is a common occurrence. Others highlight the possibility of the subdomain being included in publicly accessible configurations or code repositories like GitHub, or being discovered through certificate transparency logs. Some commenters suggest checking the server logs for clues, and emphasize that finding a subdomain doesn't necessarily imply anything nefarious is happening. The general consensus leans toward the discovery being unintentional and automated.
The Hacker News post "Ask HN: How did the internet discover my subdomain?" generated several comments offering various explanations and suggestions to the original poster (OP).
Several commenters focused on the likelihood of DNS propagation. They explained that even though the OP believed they hadn't publicly exposed their subdomain, the very act of configuring it within their DNS settings likely triggered its propagation across DNS servers. This means the subdomain became visible to parts of the internet, potentially through DNS queries made by various entities, including search engine crawlers, security scanners, or even malicious bots actively scanning for new domains.
Another popular theory revolved around misconfigured services or exposed APIs. Commenters suggested the possibility of a service running on the subdomain being inadvertently accessible from the public internet, perhaps due to a firewall misconfiguration or overly permissive access rules. They also suggested checking for publicly accessible APIs that might have revealed the subdomain's existence.
Some comments touched upon the possibility of certificate transparency logs. These logs publicly record SSL/TLS certificates issued for websites, and if the OP had obtained a certificate for their subdomain, it would be logged and thus discoverable.
A few commenters mentioned the potential role of link rot analysis tools and web crawlers. These tools constantly scan the web for broken links, and if a link to the OP's subdomain existed somewhere, even if obscure or unintended, it could have been discovered this way. Likewise, generic web crawlers might have stumbled upon the subdomain through various means and indexed it.
Several users offered practical advice to the OP, recommending using tools like
digto trace DNS records and identify potential points of exposure. Others advised checking server logs for any unusual activity that might indicate how the subdomain was discovered.A more speculative, but still plausible suggestion, involved the possibility of the subdomain being guessed or brute-forced. While less likely for a complex or randomly generated subdomain name, it is not impossible, particularly if the name is based on common patterns or easily guessable words.
Finally, some comments highlighted the inherent difficulty of fully controlling information propagation on the internet. Once something is even briefly exposed, it can be difficult to completely erase its trace. They emphasized the importance of proactive security measures and careful configuration to minimize unintended exposure.