Eric,
The way it comes across is you have some system that fakes actual passwords
being in documentation files without them actually being there, and this sounds
incredibly complicated and error-prone.
What would be a LOT better is to never even pretend or fake having passwords
where they shouldn't be, never put them in your documentation even temporarily.
Instead, have a system of named variables or entities where all your actual
documents simply indicate the name of a password, an identifier that itself is
not secret nor needs to be changed.
Then when someone is reading a document that talks about secrets, rather than
seeing the secret/password itself, they see the non-secret name, and then they
take that name and provide that to the secret server to get the actual password.
The secret names should be descriptive enough that people have an idea what they
are and if the secret server has a list of name-value pairs one can maintain
those easily enough independently.
So never put your passwords in your non-secret files to begin with.
-- Darren Duncan
On 2020-04-10 2:05 p.m., e2o wrote:
Hello!
So, I use BBEdit to write detailed client notes for my IT consulting clients. My
company came up with a new format in which we have to keep notes, and in this
"improved" standard, passwords cannot be stored in the documentation. (The idea
is that rather than passwords, links to items in a secure SecretServer (Thycotic
software) will be in the documentation.)
Anyway, I'll be forced to keep my notes in this central repository current, but
there is no way I can efficiently work from a remote repository with passwords
separate from other content. So I'll have to remove passwords from my text
documents regularly, and copy the redacted notes to the central store. I know
there is probably dozens of clever ways to tag the passwords and remove them in
one simple multi-file replace, but if anyone has a nice workflow they have
created to do something similar, I'd love to hear it before cobbling together
some hack.
Thanks!
- eric
--
This is the BBEdit Talk public discussion group. If you have a feature request or need
technical support, please email "supp...@barebones.com" rather than posting here.
Follow @bbedit on Twitter: <https://twitter.com/bbedit>
---
You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bbedit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bbedit/53cac715-7f65-27de-aa88-42949b162675%40darrenduncan.net.
