{"id":114077,"date":"2024-03-03T12:26:07","date_gmt":"2024-03-03T10:26:07","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/github-vklyuchil-po-umolchaniyu-sistemu-zashhity-ot-utechek-tokenov-k-api"},"modified":"2024-03-03T12:26:07","modified_gmt":"2024-03-03T10:26:07","slug":"github-vklyuchil-po-umolchaniyu-sistemu-zashhity-ot-utechek-tokenov-k-api","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/github-vklyuchil-po-umolchaniyu-sistemu-zashhity-ot-utechek-tokenov-k-api","title":{"rendered":"GitHub has enabled API token leak protection by default.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
GitHub has announced the default inclusion of a mechanism to prevent confidential data from inadvertently entering public repositories, which developers might leave in the code. For example, configuration files containing database passwords, tokens, or API access keys can end up in a repository. Previously, scanning was done in passive mode and allowed detection of leaks that had already occurred in the repository. Now, the check is performed automatically at the publishing stage (git push) and results in a warning if commits are detected containing confidential data. <\/p>\n
Over 250 templates have been implemented to detect various types of keys, tokens, certificates, and credentials. To minimize false positives, only guarantees of definable token types are checked, covering over 180 different services, including Amazon Web Services, Azure, Crates.io, DigitalOcean, Google Cloud, NPM, PyPI, RubyGems, and Yandex.Cloud. After a potential leak is detected, the developer is prompted to review the problematic code, address the leak, and re-commit or mark the block as false. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"