When working with distributed systems generally the more logs, the better — the complication lies in being liberal for visibility while being conservative to keep sensitive information private and secure. It’s not easy, just ask and Twitter who found themselves logging raw passwords recently. GitHub The details of GitHub’s and Twitter’s incidents weren’t made public but I’d guess an changed a log level config or logged the request bodies without realizing the consequences. engineer The fact is this is the reality of the job — with complex systems like these no one can know the consequences of every change, especially so with the fast tech turnover rate. If we’re gonna solve problems like these we need to go deeper. Issues like this arise by Murphy’s law: whatever can go wrong, will go wrong — if you leave a trap behind someone will walk into it. Let’s not do that. When writing Go, here’s what I do to leave no such trap behind and prevent the logging of secrets. Let’s say you have a sign up request like so: type CreateUserRequest struct {Credentials Credentials `json:”credentials”`} type Credentials struct {Email string `json:”email”`Password string `json:”password”`} And let’s say you’re logging to JSON for Elasticsearch: // logger we’re usinglogger := log.NewJSONLogger(os.Stdout) // request we decodedrequest := CreateUserRequest{Credentials: Credentials{Email: “ ”,Password: “theonering”,},} bilbro@theshire.net // our call to log the requestlogger.Log(“request”, request) // the output{“request”:{“credentials” {“email”:” ”,”password”:”theonering”}}} bilbro@theshire.net The result is the user’s password is logged. Not good. To solve the problem we’ll implement our own MarshalJSON that’ll redact the user’s password. func (co Credentials) MarshalJSON() ([]byte, error) {type credentials Credentialscn := credentials(co)cn.Password = "[REDACTED]"return json.Marshal((*credentials)(&cn))} Now when we log the same request the user’s password is not logged: // the output{“request”:{“credentials”:{“email”:” ”,”password”:”[REDACTED]”}}} bilbro@theshire.net There is now no possibility of logging the user’s password, regardless of who logs, nor where or when — at least if you’re logging JSON with this implementation. If you’re logging in another format, the same technique applies and there should be a corresponding marshal method for you to implement. – Please say hi at . @travisjeffery Hit the 👏 and share if you found this useful. Thanks for reading.

Keep passwords and secrets out of your logs with Go

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Handling errors in gRPC and go-kit services

104 Stories To Learn About Go

10 Questions for Aswin Ganesh, Noonie Nominee for Functional Programming

3 Golang Pitfalls Every Developer Needs to Know

207 Stories To Learn About Golang

2 Error-Free Options for Decimal handling in Golang

Handling errors in gRPC and go-kit services

104 Stories To Learn About Go

10 Questions for Aswin Ganesh, Noonie Nominee for Functional Programming

3 Golang Pitfalls Every Developer Needs to Know

207 Stories To Learn About Golang

2 Error-Free Options for Decimal handling in Golang

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps