First, thanks Roland.

>On-disk encryption is not meant to secure access on a running machine.
This is very true. And the reason for my thoughts on that topic.

> I don't think there is something like that can be easily done. You'd
> have to alter the semantics of systems calls like open(2) and read(2) to use
> passwords.

Changing the syscall's is also an interesting idea. That however would basicly 
change the host system in it's inner workings.
Now, it would imply some changing of kernel related code base, with 
decision/distinguish on type of files. And in a case of encrypted file
to use the beforehand added open_enc()/close_enc() ... syscall(s). Still this 
would make it possible to work with normal files, but also apply the 
functionality
of runtime encryption. In difference to an extra layer of fs this possibly 
would be very unportable on the first thought.Nevertheless, i like the idea.

Best regards,
 Marco

Roland Smith wrote:
> On Fri, Jan 16, 2009 at 02:59:34PM +0100, Marco wrote:
>   
>> Hello List,
>>
>> i'am using the geom framework for quite a time. I'am happy about
>> gbde/geli implementations(beside the race condition in geli) however, i
>> wonder since some time, as the data may get
>> exposed on a running server(as the partitions decrypted) 
>>     
>
> On-disk encryption is not meant to secure access on a running machine.
>
> File and directory contents are only decrypted in memory, not on disk
> when you read them. You should use normal file permissions and possibly
> ACL's to restrict access to mounted filesystems.
>
> There are of course data structures in the kernel that contain decrypted
> information about the volume. But if an attacker can grab that info from
> a running kernel you've got bigger problems...
>
>   
>> is there a way
>> to do some kind of runtime de/encyrption, with keys? so that only
>> special users with the right handle can encrypt or decrypt data? so
>> talking about another filesystem layer...
>>     
>
> I don't think there is something like that can be easily done. You'd
> have to alter the semantics of systems calls like open(2) and read(2) to use
> passwords.
>
> Roland
>   

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to