Filesystem security stuff

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C1DC4A.4E1898D0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dear all,
I am  planning to add some cryptographic properties (file encryption and =
digital signature on file I/O) to Linux filesystem. In detail, I want =
that user can do file I/O with encrypted files like he used to do with =
usual file except some minor changes (e.g. supply key for decrypting =
file). For digital signature, all read and write acts on file of any =
user must be signed and recorded so that someone else can give concrete =
evidences that a user did something on files later on.
At the first glance, I think I should implement new system calls for =
file I/O with encrypted files and add sign procedure to current file I/O =
system calls. Since I don't know much about kernel programming, VFS, =
ext2 or ext3 filesystem then I don't know where I should start. Can =
anybody give me some hints?
Thanks,
Dang Nguyen Duc


------=_NextPart_000_0009_01C1DC4A.4E1898D0
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dear all,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I am&nbsp; planning to add some =
cryptographic=20
properties (file encryption and digital signature on file I/O) to Linux=20
filesystem. In detail, I want that user can do file I/O with encrypted =
files=20
like he used to do with usual file except some minor changes (e.g. =
supply key=20
for decrypting file). For digital signature, all read and write acts on =
file of=20
any user must be signed and recorded so that someone else can give =
concrete=20
evidences that a user did something on files later on.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>At the first glance, I think I should=20
implement&nbsp;new system calls for file I/O with encrypted files and =
add sign=20
procedure to current file I/O system calls. Since I don't know much =
about kernel=20
programming, VFS, ext2&nbsp;or ext3 filesystem then I don't =
know&nbsp;where I=20
should start. Can anybody give me some hints?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Dang Nguyen Duc</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0009_01C1DC4A.4E1898D0--






[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux