Black Boar Security Inc. | Locators
For decades, the Uniform Resource Locator (URL) identified documents and their components. The emergence of AI and microservices brought major changes to this space.
Copyright© Schmied Enterprises LLC, 2024.
Link of the day.
AI based HR. Here.
Link of the day.
Robotic metal 3D printing. Here.
Link of the day.
Key developments shaping the next decade. Here.
Link of the day.
N100 Mini PC. Here.
Link of the day.
ABB Global. Here.
Link of the day.
Software firm Odoo hits $5.3 billion valuation. Here.
Link of the day.
Swiftmaps. Here.
Link of the day.
Istanbul bucket list. Here.
Link of the day.
Rabbit OS. Here.
Link of the day.
Holiday cruise private rentals. Here.
Link of the day.
AI chip fund. Here.
Link of the day.
How Bitcoin mining works. Here.
Link of the day.
Meta to offer less personalized ads in Europe. Here.
Link of the day.
What is Labubu? Here.
For a long time, URLs have been key targets for attackers. Only the fully qualified domain name is signed, leaving other parts at risk. Law enforcement and private security agencies can insert a private certificate authority into the corporate system and propagate it through group policies, allowing easy surveillance.
This method could compromise banking, messaging, and trading systems, allowing them to be circumvented, tapped, or tampered with. To counter these threats, companies introduced workarounds such as captchas and two-factor authentication.
Locators serve many roles.
They identify a service's domain, which was traditionally a cryptic address like google.com. In the long run, relying on a registered trademark may become the preferred solution.
Name services once translated each domain into a numeric internet address, and this process was traditionally not encrypted pointing to some attackers. Google started to rotate their graphics daily. Even encrypted name services can pose problems under existing certificate authority standards. Our solution includes storing machine addresses with the domain, creating a signed and verified record that supports multiple addresses for load balancing or geographic latency optimization.
The https scheme once described the type of service, but it now appears outdated and cryptic to newcomers. As the saying goes, there are no old jokes, just old people, because jokes are always new to children. In this context, the service can be included as part of the signed locator.
Paths once indicated the location of a document, while search tags highlighted a specific point of interest within it. Both elements can now be merged into a single path.
Finally, name services traditionally connected users to the correct machine. However, in the microservices era, this approach is outdated. A simpler method might involve adding one or two name services for verification purposes.
One example of a simplified locator could be 8.8.8.8/Google/10.0.0.5,10.0.0.3 of Canada/Gemini/Attachment Service/Documents/Readme/Attachments. This format resolves the name service, trademark, addresses, locations, microservices, path, and item in one string. It may even be simpler for the new generation to understand.