On Friday, December 27, 2024 at 7:17:41 PM UTC-6 Dan Kortschak wrote: On Fri, 2024-12-27 at 17:01 -0800, Jeffery Carr wrote: > I won't go into the nefarious reasons here. Let's just say it's going > to have to be fixed. > > Cryptographically signing this is bad.
This kind of argument is unlikely to result in any change. If there is something that you have knowledge of that would impact on the design, file an issue (or if it is a security issue, send to secu...@golang.org as described in go.dev/doc/security/policy). Okay, maybe. I'm posting here on this forum about being dumb and making mistakes where I need a "go-delete" option. I'm not sure it sounds like a good idea to email security professionals about why making a cryptographic blockchain available in real time everywhere that allows anyone to arbitrarily insert information into it permanently might be a bad idea! I think they probably would already know. Anyway, if the transparency log can be be created by domain, then there can be a way to delete and recreate it. That would be helpful here. We need "go-delete". Security is not important to us. There should be a balance between people that need security and people that don't need it. jcarr (maybe I will email that email address perhaps. thanks for the information) -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/a8939807-c01b-4924-85c4-9e9a85f748ffn%40googlegroups.com.
