[maemo-developers] Security Guidance for N800 OS development

From: Acadia Secure Networks acadiasecurenets at aol.com
Date: Wed Feb 21 19:39:44 EET 2007

feel free to put it to bed for now.

Nonetheless, I hope and believe that this group  will continue to look 
for ways to make the N800 a more secure mobile device. Here are a few 
more items I can think of for consideration by Nokia itself:

    1. An option for keeping sensitive data on the device encrypted.
    This is important for dealing with the fact that mobile devices get
    stolen and, more often lost.

    2. An option in the improved mail client, whenever that arrives from
    Nokia ,for supporting encrypted email payload and sender authentication.

I should add that the "someone" to whom security is important is, at a 
minimum, the corporate user, should the N800 device become (as I think 
it can become) a useful device in the corporate environment.

A large and looming  issue on the "plates" of the corporate it staffs 
these days is managing the proliferation of mobile devices 
(pda's/notebooks/smartphones, etc.) that can and do drill into the  
interior of the  corporate network to access different applications that 
process sensitive company information.

Best Regards,


John Holmblad


Mike Lococo wrote:
> This thread should really be put to bed.  The only concrete action 
> item that has emerged from it is a request for the inclusion of 
> iptables, which is duly noted.  Iptables is one clearly useful tool 
> for limiting access to a daemon based on source IP.  Since none of the 
> devices ship with any daemons running by default, this is likely to be 
> a low priority for Nokia engineers.  It is, nonetheless, worth noting 
> that it would provide 3rd party developers and and power users with 
> options for limiting access to user-installed daemons.
> If this is important to someone, they should build a kernel package 
> with the feature enabled.  If it generates interest, we'll be in a 
> much better position to petition Nokia for the feature than by 
> discussing it in a vacuum as is currently happening.
> Thanks,
> Mike
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20070221/e8a21acd/attachment.htm 
More information about the maemo-developers mailing list