simple solution would be to just create a stream interface based driver and write to it whatever you want to. If you want to actually do some key\secret exchange, implement some ioctl calls for it....but again, i think you should do your data manipulation in app layer and then just send that data to the kernel driver to let it do the transport handling....
On Tue, Oct 20, 2009 at 8:40 AM, Jerome Hwang <jhwan...@gmail.com> wrote: > > yea you can say that as "encrypted channel" > > I just want to study how Applications now use what kind of functions > or ways to transmit data to kernel > so probably later I can try to write my own "channel" so that > application can bypass "Library" and "Application Framework" level > > any idea? > > On Oct 20, 10:15 am, Abhinayak Mishra <abhina...@gmail.com> wrote: > > Do you mean if there exists an "encrypted channel" between the framework > and > > the kernel? Why do you need that? do you want to send data to kernel over > > this "secure" channel and then extract the data again in kernel do some > > stuff on it and then transmit? > > Why not do all your data manipulation in the app layer itself and just > use > > the kernel layer to do the transport handling? > > > > > > > > On Tue, Oct 20, 2009 at 6:28 AM, Jerome Hwang <jhwan...@gmail.com> > wrote: > > > > > Hi All, > > > > > I recently want to write a driver tunneling stuff > > > > > but first I have to figure out what are the Secure ways to transfer > > > data from "Application Framework" and "Library" to Kernel. > > > > > Any Idea? > > > > > thanks, > > > Jerome Hwang > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
