Pankaj,
Not wanting to put you off, but the Git inernals do include more than the
common data model methods for the object store. In particular there is the
idea of a pack file which has a highly compressed version of a large number
of the objects compacted into the one file.
It's probably easier to let the encryption be at file system level and let
the hard drive handle it - maybe.
Philip
----- Original Message -----
From: "Pankaj Azad" <pankaja...@hotmail.com>
To: "Git for human beings" <git-users@googlegroups.com>
Sent: Tuesday, January 23, 2018 8:27 PM
Subject: [git-users] Feature Request
Support for encryption at git objects level will be a step in making the git
repositories secure. The way I envisage it to work is following.
1. Git takes the objects as usual, computes sha1 and performs compression
2. Just before the contents are stored in file, it applies encryption on
each git object.
3. Similarly the first thing it does after reading a file is decryption
4. This way it'll be transparent to the user
The mechanism/command to use for encryption can be made configurable by the
user. i.e. a user configured program/command will be invoked to get the git
objects' contents encrypted/decrypted. So the users free to use encryption
tool of their choice, or not use anything at all. In that case it'll be a
regular git repository.
--
You received this message because you are subscribed to the Google Groups
"Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
