"currently" sounds like that might change in the future. I thought the CA/B forum was pretty much opposed to non-EV certs for .onions. Is that not the case? What is the potential use case for non-EV certs on a .onion?
The EFF's representative to CA/B (Seth Schoen) suggested that DV certs for .onion make sense in the v3 onion service world.
There wasn't exactly rapturous support, but there were constructive comments from some of the usual suspects on the Browser side of the equation. So far I as know/ remember this discussion died out without anybody producing an actual ballot that could be voted on.
Most notably there wasn't a fierce backlash of CA reps yelling that this was an awful idea and they wanted no part in it. So either they're OK with it, or they've decided it won't go anywhere and they don't care. Without a ballot changing the actual Baseline Requirements you'd never know for sure.
Personally I'm not convinced DV .onion certificates are a great idea, but I'm not opposed to them either, and it seems some people who own .onion services that aren't legal, or need to be anonymous for whatever reason would like to have such certificates.
"currently" sounds like that might change in the future. I thought the CA/B forum was pretty much opposed to non-EV certs for .onions. Is that not the case? What is the potential use case for non-EV certs on a .onion?