"the trademark issue is now resolved", amazing.
They clearly wanted to put them out of business because they see them as a competitor!
Comodo has filed for express abandonment of LetsEncrypt trademark applications
91–96 of 96 posts
Re: Comodo has filed for express abandonment of LetsEncrypt trademark applications
#92Earlier quoted context omitted.
I remember reading an article a while back (couldn't find it through Google) that talked about how people with abusive tendencies (which this kind of tortured diatribe seems adjacent to) have an accompanying tendency to psychologically distance themselves from their actions by avoiding first-person constructions, eg. "and then it happened" instead of "and then I did it". That being said, it sounds like the cause of t…
Here's another example of what I'm talking about from a recent post on HN [0]. Specifically in that post, an email correspondence goes like this: "Thought sharing this framework with you prior to our convo would make it more efficient. Would love to get your perspective on this when we chat in the morning (your evening)." See the weird omission of reference to self? Here's something I didn't originally intend to shar…
The historical example that comes to mind is telegrams, where the sender was charged per word, and consequently people omitted as many words as possible while keeping the message on the right side of comprehensible. Sometimes just barely; Wiki gives this example telegram from Orville Wright:
"Success four flights thursday morning all against twenty one mile wind started from Level with engine power alone average speed through air thirty one miles longest 57 seconds inform Press home Christmas"
I sometimes omit first-person pronouns and some other words when writing text messages, because I find it considerably more difficult to type there. The charitable interpretation I would give is that, if someone writes emails like this, either they're writing on an inconvenient mobile platform now, or they're used to writing on such a platform and write that way even with a proper keyboard.
Re: Comodo has filed for express abandonment of LetsEncrypt trademark applications
#93HackerNews has won!
not really, hn still uses certs from comodo. cloudflare still uses certs from comodo. cloudflare and hn dropping comodo would have been close to a win
Re: Comodo has filed for express abandonment of LetsEncrypt trademark applications
#94Re: Comodo has filed for express abandonment of LetsEncrypt trademark applications
#95We are switching our Comodo certs over to Let's Encrypt because certain old Android versions we have to support work with LE certs but not with Comodo. Particularly important for APIs. The 90 day expiry is a bit of a faff, but we've mostly automated it using acme.sh and automated DNS edits, and now we just need load balancer access (we just moved to new hosts). LE is a godsend and fully up to commercial use in our ex…
I've dealt with this issue for years. Comodo certs have two possible chains. If you want to be supported by older Android (and older iOS) devices, you needed to configure your server to hand out the longer of the chains. When you buy a cert, this is not the chain they will recommend. This is easy under Linux if you can find the right certs, a huge PITA if you're on IIS. They do an incredibly poor job of documenting t…
We switched to Let's Encrypt literally because of this, so that's a direct penalty for their stupidity on this one ;-)
Do you know a writeup anywhere of the cert chain issue? (I ask for idle amusement, no way we're going back to them.)
Oh, and when I say "fully up to commercial use", we plan to use LE certs for our dev instances too (so we're SSL at all stages of development).
Re: Comodo has filed for express abandonment of LetsEncrypt trademark applications
#96Earlier quoted context omitted.
I've dealt with this issue for years. Comodo certs have two possible chains. If you want to be supported by older Android (and older iOS) devices, you needed to configure your server to hand out the longer of the chains. When you buy a cert, this is not the chain they will recommend. This is easy under Linux if you can find the right certs, a huge PITA if you're on IIS. They do an incredibly poor job of documenting t…
We switched to Let's Encrypt literally because of this, so that's a direct penalty for their stupidity on this one ;-) Do you know a writeup anywhere of the cert chain issue? (I ask for idle amusement, no way we're going back to them.) Oh, and when I say "fully up to commercial use", we plan to use LE certs for our dev instances too (so we're SSL at all stages of development).
No write up anywhere that I ever found. The best investigative tool is the SSLLabs SSL test, which will show you both possible paths from the cert. By looking at which certificates that test shows the server provided, you can divine which path things are going to take.
If you find yourself landing at a root CA which is newer and not trusted by as many devices, those devices won't intelligently realise it's cross-signed, unless you switch the certs the server offers to send them up that path.