★ wanayoo — archive 1999 http://icewalkers.com/doclib/howtos/Secure-Programs-HOWTO/x638.htmlNouvelle recherche | Portail wanayoo
Name:   Pass:    
Subscribe to IceWalkers Free NewsLetter




















Linux2000 OnLine
see all



Year 2000 most disappointing thing was:

Y2K Bug
NASDAQ
Delayed Linux Kernel 2.4
Butterfly ballots
Pentium IV
Nothing. That was a great year!

  View results
  Previous polls
 
 Search Howtos: Match: Sort by:



Linux HOWTOs  |  HOWTOs Index



Secure the Interface

6.1. Secure the Interface

Interfaces should be minimal (simple as possible), narrow (provide only the functions needed), and non-bypassable. Trust should be minimized. Consider limiting the data that the user can see.

Applications and data viewers may be used to display files developed externally, so in general don't allow them to accept programs (also known as ``scripts'' or ``macros'') unless you're willing to do the extensive work necessary to create a secure sandbox. The most dangerous kind is an auto-executing macro that executes when the application is loaded and/or when the data is initially displayed; from a security point-of-view this is a disaster waiting to happen unless you have extremely strong control over what the macro can do (a ``sandbox''), and past experience has shown that real sandboxes are hard to implement.



HOWTOs Index

 
  
 
 
 


FOX 0.99.160
Code Forge IDE 1.6.5
Firestarter 0.6.1
QCad 1.4.6
galeon 0.10.1
cdrecord 1.10a14-2
lilo 21.7
PostgreSQL 7.1beta5



GnomeICU 0.96
FVWM 2.2.5
gcombust 0.1.42
Smalltalk 1.95.3
cfengine 1.6.3
Linberto 1.0.5
LilyPond 1.3.132
GTK+ Object Builder 1.0.7
fcron 1.0.1
gif2png 2.4.1
ImPress 1.1-b7
dhcpcd 1.3.19-pl7
WebSupport 2.0.11
Partition Image 0.5.4
Komba 0.7
Ishmail 2.0.0
libxml 2.3.2