_LOG_SOCKET = None
OUR_PROGNAME = "configure-syslog"
-LOGGLY_AUTH_TOKEN = "f5b38b8c-ed99-11e2-8ee8-3c07541ea376"
+LOGGLY_AUTH_TOKEN = "MWVjNGU4ZTEtZmJiMi00N2U3LTkyOWItNzVhMWJmZjVmZmUw" https://configsyslog.gen2.loggly.com/tokens doesn't seem to have this token. Do we want to encode 1ec4e8e1-fbb2-47e7-929b-75a1bff5ffe0 instead?
—
Reply to this email directly or view it on GitHub.
ProTip!
Use n and p to navigate between commits in a pull request.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
Learn more.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
You can always update your selection by clicking Cookie Preferences at the bottom of the page.
For more information, see our Privacy Statement.
Essential cookies
We use essential cookies to perform essential website functions, e.g. they're used to log you in.
Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they're used to gather information about the pages you visit and how many clicks you need to accomplish a task.
Learn more
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rhigdon updates merge and obfuscate #29
Rhigdon updates merge and obfuscate #29
Changes from all commits
9a385910b9eb2cFile filter...
Jump to…
ivangonekrazyAug 31, 2013
Contributor
https://configsyslog.gen2.loggly.com/tokens doesn't seem to have this token. Do we want to encode
1ec4e8e1-fbb2-47e7-929b-75a1bff5ffe0instead?ivangonekrazyAug 31, 2013
Contributor
verified the actual token is encoded in there.
vinhnAug 31, 2013
Why obfuscate? If the customer configured this by hand, they'd need to see the raw auth token (which they'd own), and configure using the raw value.
By obfuscating it here, I'm sure a user will wonder if they need to do the same if configuring things manually.
Same thing in examples on how to post events via HTTP. Those examples must show the raw auth token. So we should be consistent here.
On Aug 30, 2013, at 6:41 PM,♥ Ivan Tam ♥ notifications@github.com wrote: