Currently the password storage is optional, but may be useful to automate the update.
To prevent someone from easily spying on the password, a simple local encryption with a locally stored "master" password would help. It certainly doesn't prevent anyone from combining both and decrypting the passwords, but it helps against over-the-shoulder "attacks", which should be enough for most cases.
Currently the password storage is optional, but may be useful to automate the update.
To prevent someone from easily spying on the password, a simple local encryption with a locally stored "master" password would help. It certainly doesn't prevent anyone from combining both and decrypting the passwords, but it helps against over-the-shoulder "attacks", which should be enough for most cases.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently the password storage is optional, but may be useful to automate the update.
To prevent someone from easily spying on the password, a simple local encryption with a locally stored "master" password would help. It certainly doesn't prevent anyone from combining both and decrypting the passwords, but it helps against over-the-shoulder "attacks", which should be enough for most cases.