<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on NTNINJA</title><link>https://ntninja.com/categories/security/</link><description>Recent content in Security on NTNINJA</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Ryan Johnson</copyright><lastBuildDate>Mon, 21 Nov 2022 15:00:00 -0500</lastBuildDate><atom:link href="https://ntninja.com/categories/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Protecting Repos with Encrypted GIT</title><link>https://ntninja.com/posts/encrypted-git/</link><pubDate>Mon, 21 Nov 2022 15:00:00 -0500</pubDate><guid>https://ntninja.com/posts/encrypted-git/</guid><description>&lt;p&gt;Open source software development is great, and there exists an abundance of difference git solutions to create public and private repositories for collaboration and distribution.
Private repos give you an extra layer of control by not allowing your code base to be seen by the public.
Occasionally you may have a project that you want to be able to collaborate with a limited set of remote people, and want restrict the possiblity of your source being viewed, even by the git service provider.
None of the commercial git providers have a good solution for this currently, at least that I know of.&lt;/p&gt;</description></item></channel></rss>