> <i>This is the support email address you are looking for: ac-mobile-feedback@cisco.com</i><p>Thank you. I have a bunch of curl tech support questions, but didn't know who to contact.
Similar misdirection situation with <i>"sqlite_"</i> files and the attempt to obfuscate with <i>"etilqs_"</i> to redirect users to the offending software :<p><a href="https://github.com/sqlite/sqlite/blob/33c120f9b7de84fb0dd2625efe11097015c0e116/src/os.h#L65-L75">https://github.com/sqlite/sqlite/blob/33c120f9b7de84fb0dd262...</a><p>(commit dated 2006-10-31: <a href="https://github.com/sqlite/sqlite/commit/fd288f3549a1ab9a309a9e120d46319d42adea29">https://github.com/sqlite/sqlite/commit/fd288f3549a1ab9a309a...</a>)<p><a href="https://www.google.com/search?q=etilqs" rel="nofollow">https://www.google.com/search?q=etilqs</a>
It is kind of telling how we accept that companies hide their support channels in every conceivable way and that this leads to random and arbitrary contact points sticking out more than the official ones.
I used to “own” a port in /etc/services and got a few
Emails and somehow a very irate phone call from someone that was being port scanned. (Back when we had desk phones and they could call the company main number and asked to be transferred.)
From the Mastodon comments, we have @timbray:<p><i>Not trying to be competitive, but over the years, my email flow along the lines of “My XML file isn’t working” (my email is on the front page of the spec) was occasionally um substantial. Sympathy.</i><p><a href="https://cosocial.ca/@timbray/113587445812736554" rel="nofollow">https://cosocial.ca/@timbray/113587445812736554</a>
Daniels email collection is also funny [0].<p>[0] <a href="https://daniel.haxx.se/email/" rel="nofollow">https://daniel.haxx.se/email/</a>
Hahah! That has happened with me too. I used to work on car infotainment systems in India's biggest automobile company. After the NDA cooled off, I added the work I did on my portfolio to apply for future roles. The thing we made was amazing (for that time 2015) as it allowed people with low-end infotainments with mono color displays to have navigation support using mobile.<p>People saw it on my blog and sent me service queries.
My company has a name that (if you squint really, really hard) can be confused with Logitech.<p>So naturally, I got a few questions on topics such as non working mice or keyboards, headphones and similar.<p>My usual reply lately (not that many, I can still bother to reply) is "This is not the Logitech you are looking for..." with the link to the company they want.
I worked for the CSIRO division of information technology. In pre widespread internet days people found me in the phone book and wanted information about technology: typically, the dangers if their Teflon saucepan had shed into their food.
Poor guy. After being misidentified as a threat to the us, he's having to field support requests for a malicious company. (They made it hard for people to get support for their paid product)
This reminds me of the "etilqs_" files. <a href="https://news.ycombinator.com/item?id=36302805">https://news.ycombinator.com/item?id=36302805</a>
To be fair, the curl license doesn't mention "curl" anywhere in it. It seems reasonable for someone to interpret "this software" as referring to the software product that includes the license.
I wonder if they still use a version of cURL from 2006. <a href="https://daniel.haxx.se/blog/wp-content/uploads/2016/10/curl-cisco-anyconnect.jpg" rel="nofollow">https://daniel.haxx.se/blog/wp-content/uploads/2016/10/curl-...</a>
This reminds me on how Spotify's bug bounty program keeps receiving vulnerability reports about Shopify, and how Shopify keeps receiving vulnerability reports from Spotify. This went so far that they had to explicitly put the other company's domain as out of scope on their bug bounty policy.