With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.įortunately, distribution rights do not apply for internal use. If you are an organization using Chocolatey, we want your experience to be fully reliable.ĭue to the nature of this publicly offered repository, reliability cannot be guaranteed. Human moderators who give final review and sign off.Security, consistency, and quality checking.ModerationĮvery version of each package undergoes a rigorous moderation process before it goes live that typically includes: The “advanced” approach uses the plugin Keecloud.Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community. However, in this configuration you need to close the database after a change so that it is re-uploaded to the cloud. There is the “simple” approach to simply put the database on the synced cloud folder, and to open it from here everytime. We’ll use Dropbox to store our database in the cloud. This is why I use the password generator from Keepass, with at least 12 characters (alphanumerics, punctuation and specials)įor those passwords that I try to remember, sometimes I use the plugin Pronounceable Password Generator. Hence why we are using a password manager.

The conclusion is that a strong password is difficult to remember. Not using terms already present in “dictionnaries” used for attacks.True randomness (a thing at which humans are weak).The TL DR version of the article boils down to I find that this article from Wired is a very good resource to read to understand the issue. There are lot’s of discussions and tutorials on how to generate a strong password. Keepass database creation menu Using a “strong” password