Best practices for obscuring sensitive information Topic is solved

Get help with using AutoHotkey (v2 or newer) and its commands and hotkeys
the_alchemist
Posts: 5
Joined: 19 May 2023, 10:39

Best practices for obscuring sensitive information

Post by the_alchemist » 19 May 2023, 10:44

I would like to use version control to manage my code. In the spirit of open source I would like to make my repositories public. However, my scripts may contain sensitive information like my email or home address. What is the favorable method of obscuring this information?

guest3456
Posts: 3465
Joined: 09 Oct 2013, 10:31

Re: Best practices for obscuring sensitive information

Post by guest3456 » 19 May 2023, 11:40

move the sensitive info to a config file, and have your project read from the config file

then use a .gitignore file to ignore the config file so it doesnt go into the repo


swagfag
Posts: 6222
Joined: 11 Jan 2017, 17:59

Re: Best practices for obscuring sensitive information

Post by swagfag » 19 May 2023, 11:42

create and query Environment Variables on ur computer

the_alchemist
Posts: 5
Joined: 19 May 2023, 10:39

Re: Best practices for obscuring sensitive information

Post by the_alchemist » 20 May 2023, 09:19

Is there a built-in system for reading from config files? Or do I have to write my own logic for that using FileRead? If there isn't, I guess getting system environment variables will be much smoother.

User avatar
boiler
Posts: 17328
Joined: 21 Dec 2014, 02:44

Re: Best practices for obscuring sensitive information  Topic is solved

Post by boiler » 20 May 2023, 10:06

the_alchemist wrote: Is there a built-in system for reading from config files?
IniRead


Post Reply

Return to “Ask for Help (v2)”