Toyota Accidently Exposed a Secret Key Publicly on GitHub for Five Years

Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by rytis on Friday October 14, 2022 @02:13AM (#33200175)

And while we're at it, I think saving two chars isn't going to do much to prevent global warming, and let's just use more readable SERVICE_{KEY} and SERVICE_PUB_{KEY} (as opposed to having scratch your head thinking "did I call it SRV, SVC, SRVC, SRVCE, ...?")

[ Parent | on HN ]

Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by hawski on Friday October 14, 2022 @04:41AM (#33201090)

I think OP meant to use the actual name of the service. For example FOOBARINC_{KEY}

I also think that it should look just a bit cryptic to make a person unsure if they can meddle with the string.

[ Parent | on HN ]

Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub... by gl-prod on Friday October 14, 2022 @03:37AM (#33200656)

I meant as an abbreviation, like GitHub becomes ghp_XXXXXXXXX. But yeah anything is better than just random characters.

[ Parent | on HN ]