flavors-stable rev 113
firefox: remove old files
| author | Christophe Lincoln <pankso@slitaz.org> |
|---|---|
| date | Tue May 31 01:13:09 2011 +0200 (2011-05-31) |
| parents | 97f1736b586c |
| children | 6892605beb55 |
| files | firefox/rootfs/etc/daemons.conf firefox/rootfs/etc/init.d/wpa_supplicant firefox/rootfs/etc/wpa_supplicant.conf firefox/rootfs/usr/share/applications/system-doc.desktop |
line diff
1.1 --- a/firefox/rootfs/etc/daemons.conf Tue May 31 00:45:49 2011 +0200 1.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 1.3 @@ -1,36 +0,0 @@ 1.4 -# /etc/daemons.conf - Daemons options configuration file. 1.5 -# 1.6 -# This file is used for setting options to start daemons at boot time or from 1.7 -# the command line (/etc/init.d/daemon-name start). Please check /etc/rcS.conf 1.8 -# to automatically start a daemon at boot. 1.9 -# 1.10 - 1.11 -# DBUS daemon options. 1.12 -DBUS_OPTIONS="--system" 1.13 - 1.14 -# HAL daemon options. 1.15 -HALD_OPTIONS="--daemon=yes" 1.16 - 1.17 -# LightTPD Web server options. 1.18 -LIGHTTPD_OPTIONS="-f /etc/lighttpd/lighttpd.conf" 1.19 - 1.20 -# Dropbear SSH server options. 1.21 -DROPBEAR_OPTIONS="-w -g -b /etc/dropbear/banner" 1.22 - 1.23 -# Rsync daemon options. 1.24 -RSYNCD_OPTIONS="--daemon" 1.25 - 1.26 -# Cron daemon options. 1.27 -CROND_OPTIONS="-b" 1.28 - 1.29 -# Domain Name Server options. 1.30 -DNSD_OPTIONS="-d" 1.31 - 1.32 -# Super server options 1.33 -INETD_OPTIONS="" 1.34 -# Tftp daemon options. 1.35 -TFTPD_OPTIONS="-r /boot" 1.36 - 1.37 -# wpa_supplicant daemon options 1.38 -WPA_OPTIONS="-B -P/var/run/wpa_supplicant.pid -c/etc/wpa_supplicant.conf -i$(. /etc/network.conf ; echo $WIFI_INTERFACE)" 1.39 -
2.1 --- a/firefox/rootfs/etc/init.d/wpa_supplicant Tue May 31 00:45:49 2011 +0200 2.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 2.3 @@ -1,55 +0,0 @@ 2.4 -#!/bin/sh 2.5 -# /etc/init.d/wpa_supplicant: Start, stop and restart wpa_supplicant deamon 2.6 -# on SliTaz, at boot time or with the command line. 2.7 -# 2.8 -# To start daemon at boot time, just put the right name in the $RUN_DAEMONS 2.9 -# variable of /etc/rcS.conf and configure options with /etc/daemons.conf. 2.10 -# 2.11 -. /etc/init.d/rc.functions 2.12 -. /etc/daemons.conf 2.13 - 2.14 -NAME=wpa_supplicant 2.15 -DESC="wpa_supplicant deamon" 2.16 -DAEMON=/usr/bin/wpa_supplicant 2.17 -OPTIONS=$WPA_OPTIONS 2.18 -PIDFILE=/var/run/wpa_supplicant.pid 2.19 - 2.20 -case "$1" in 2.21 - start) 2.22 - if [ -f $PIDFILE ] ; then 2.23 - echo "$NAME already running." 2.24 - exit 1 2.25 - fi 2.26 - echo -n "Starting $DESC: $NAME... " 2.27 - $DAEMON $OPTIONS 2.28 - status 2.29 - ;; 2.30 - stop) 2.31 - if [ ! -f $PIDFILE ] ; then 2.32 - echo "$NAME is not running." 2.33 - exit 1 2.34 - fi 2.35 - echo -n "Stopping $DESC: $NAME... " 2.36 - kill `cat $PIDFILE` 2.37 - status 2.38 - ;; 2.39 - restart) 2.40 - if [ ! -f $PIDFILE ] ; then 2.41 - echo "$NAME is not running." 2.42 - exit 1 2.43 - fi 2.44 - echo -n "Restarting $DESC: $NAME... " 2.45 - kill `cat $PIDFILE` 2.46 - sleep 2 2.47 - $DAEMON $OPTIONS 2.48 - status 2.49 - ;; 2.50 - *) 2.51 - echo "" 2.52 - echo -e "\033[1mUsage:\033[0m /etc/init.d/`basename $0` [start|stop|restart]" 2.53 - echo "" 2.54 - exit 1 2.55 - ;; 2.56 -esac 2.57 - 2.58 -exit 0
3.1 --- a/firefox/rootfs/etc/wpa_supplicant.conf Tue May 31 00:45:49 2011 +0200 3.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 3.3 @@ -1,754 +0,0 @@ 3.4 -##### Example wpa_supplicant configuration file ############################### 3.5 -# 3.6 -# This file describes configuration file format and lists all available option. 3.7 -# Please also take a look at simpler configuration examples in 'examples' 3.8 -# subdirectory. 3.9 -# 3.10 -# Empty lines and lines starting with # are ignored 3.11 - 3.12 -# NOTE! This file may contain password information and should probably be made 3.13 -# readable only by root user on multiuser systems. 3.14 - 3.15 -# Note: All file paths in this configuration file should use full (absolute, 3.16 -# not relative to working directory) path in order to allow working directory 3.17 -# to be changed. This can happen if wpa_supplicant is run in the background. 3.18 - 3.19 -# Whether to allow wpa_supplicant to update (overwrite) configuration 3.20 -# 3.21 -# This option can be used to allow wpa_supplicant to overwrite configuration 3.22 -# file whenever configuration is changed (e.g., new network block is added with 3.23 -# wpa_cli or wpa_gui, or a password is changed). This is required for 3.24 -# wpa_cli/wpa_gui to be able to store the configuration changes permanently. 3.25 -# Please note that overwriting configuration file will remove the comments from 3.26 -# it. 3.27 -#update_config=1 3.28 - 3.29 -# global configuration (shared by all network blocks) 3.30 -# 3.31 -# Parameters for the control interface. If this is specified, wpa_supplicant 3.32 -# will open a control interface that is available for external programs to 3.33 -# manage wpa_supplicant. The meaning of this string depends on which control 3.34 -# interface mechanism is used. For all cases, the existance of this parameter 3.35 -# in configuration is used to determine whether the control interface is 3.36 -# enabled. 3.37 -# 3.38 -# For UNIX domain sockets (default on Linux and BSD): This is a directory that 3.39 -# will be created for UNIX domain sockets for listening to requests from 3.40 -# external programs (CLI/GUI, etc.) for status information and configuration. 3.41 -# The socket file will be named based on the interface name, so multiple 3.42 -# wpa_supplicant processes can be run at the same time if more than one 3.43 -# interface is used. 3.44 -# /var/run/wpa_supplicant is the recommended directory for sockets and by 3.45 -# default, wpa_cli will use it when trying to connect with wpa_supplicant. 3.46 -# 3.47 -# Access control for the control interface can be configured by setting the 3.48 -# directory to allow only members of a group to use sockets. This way, it is 3.49 -# possible to run wpa_supplicant as root (since it needs to change network 3.50 -# configuration and open raw sockets) and still allow GUI/CLI components to be 3.51 -# run as non-root users. However, since the control interface can be used to 3.52 -# change the network configuration, this access needs to be protected in many 3.53 -# cases. By default, wpa_supplicant is configured to use gid 0 (root). If you 3.54 -# want to allow non-root users to use the control interface, add a new group 3.55 -# and change this value to match with that group. Add users that should have 3.56 -# control interface access to this group. If this variable is commented out or 3.57 -# not included in the configuration file, group will not be changed from the 3.58 -# value it got by default when the directory or socket was created. 3.59 -# 3.60 -# When configuring both the directory and group, use following format: 3.61 -# DIR=/var/run/wpa_supplicant GROUP=wheel 3.62 -# DIR=/var/run/wpa_supplicant GROUP=0 3.63 -# (group can be either group name or gid) 3.64 -# 3.65 -# For UDP connections (default on Windows): The value will be ignored. This 3.66 -# variable is just used to select that the control interface is to be created. 3.67 -# The value can be set to, e.g., udp (ctrl_interface=udp) 3.68 -# 3.69 -# For Windows Named Pipe: This value can be used to set the security descriptor 3.70 -# for controlling access to the control interface. Security descriptor can be 3.71 -# set using Security Descriptor String Format (see http://msdn.microsoft.com/ 3.72 -# library/default.asp?url=/library/en-us/secauthz/security/ 3.73 -# security_descriptor_string_format.asp). The descriptor string needs to be 3.74 -# prefixed with SDDL=. For example, ctrl_interface=SDDL=D: would set an empty 3.75 -# DACL (which will reject all connections). See README-Windows.txt for more 3.76 -# information about SDDL string format. 3.77 -# 3.78 -ctrl_interface=/var/run/wpa_supplicant 3.79 - 3.80 -# Ensure that only root can read the WPA configuration 3.81 -ctrl_interface_group=0 3.82 - 3.83 - 3.84 -# IEEE 802.1X/EAPOL version 3.85 -# wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines 3.86 -# EAPOL version 2. However, there are many APs that do not handle the new 3.87 -# version number correctly (they seem to drop the frames completely). In order 3.88 -# to make wpa_supplicant interoperate with these APs, the version number is set 3.89 -# to 1 by default. This configuration value can be used to set it to the new 3.90 -# version (2). 3.91 -eapol_version=1 3.92 - 3.93 -# AP scanning/selection 3.94 -# By default, wpa_supplicant requests driver to perform AP scanning and then 3.95 -# uses the scan results to select a suitable AP. Another alternative is to 3.96 -# allow the driver to take care of AP scanning and selection and use 3.97 -# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association 3.98 -# information from the driver. 3.99 -# 1: wpa_supplicant initiates scanning and AP selection 3.100 -# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association 3.101 -# parameters (e.g., WPA IE generation); this mode can also be used with 3.102 -# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with 3.103 -# APs (i.e., external program needs to control association). This mode must 3.104 -# also be used when using wired Ethernet drivers. 3.105 -# 2: like 0, but associate with APs using security policy and SSID (but not 3.106 -# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to 3.107 -# enable operation with hidden SSIDs and optimized roaming; in this mode, 3.108 -# the network blocks in the configuration file are tried one by one until 3.109 -# the driver reports successful association; each network block should have 3.110 -# explicit security policy (i.e., only one option in the lists) for 3.111 -# key_mgmt, pairwise, group, proto variables 3.112 -ap_scan=1 3.113 - 3.114 -# EAP fast re-authentication 3.115 -# By default, fast re-authentication is enabled for all EAP methods that 3.116 -# support it. This variable can be used to disable fast re-authentication. 3.117 -# Normally, there is no need to disable this. 3.118 -fast_reauth=1 3.119 - 3.120 -# OpenSSL Engine support 3.121 -# These options can be used to load OpenSSL engines. 3.122 -# The two engines that are supported currently are shown below: 3.123 -# They are both from the opensc project (http://www.opensc.org/) 3.124 -# By default no engines are loaded. 3.125 -# make the opensc engine available 3.126 -#opensc_engine_path=/usr/lib/opensc/engine_opensc.so 3.127 -# make the pkcs11 engine available 3.128 -#pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so 3.129 -# configure the path to the pkcs11 module required by the pkcs11 engine 3.130 -#pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so 3.131 - 3.132 -# Dynamic EAP methods 3.133 -# If EAP methods were built dynamically as shared object files, they need to be 3.134 -# loaded here before being used in the network blocks. By default, EAP methods 3.135 -# are included statically in the build, so these lines are not needed 3.136 -#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so 3.137 -#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so 3.138 - 3.139 -# Driver interface parameters 3.140 -# This field can be used to configure arbitrary driver interace parameters. The 3.141 -# format is specific to the selected driver interface. This field is not used 3.142 -# in most cases. 3.143 -#driver_param="field=value" 3.144 - 3.145 -# Maximum lifetime for PMKSA in seconds; default 43200 3.146 -#dot11RSNAConfigPMKLifetime=43200 3.147 -# Threshold for reauthentication (percentage of PMK lifetime); default 70 3.148 -#dot11RSNAConfigPMKReauthThreshold=70 3.149 -# Timeout for security association negotiation in seconds; default 60 3.150 -#dot11RSNAConfigSATimeout=60 3.151 - 3.152 -# network block 3.153 -# 3.154 -# Each network (usually AP's sharing the same SSID) is configured as a separate 3.155 -# block in this configuration file. The network blocks are in preference order 3.156 -# (the first match is used). 3.157 -# 3.158 -# network block fields: 3.159 -# 3.160 -# disabled: 3.161 -# 0 = this network can be used (default) 3.162 -# 1 = this network block is disabled (can be enabled through ctrl_iface, 3.163 -# e.g., with wpa_cli or wpa_gui) 3.164 -# 3.165 -# id_str: Network identifier string for external scripts. This value is passed 3.166 -# to external action script through wpa_cli as WPA_ID_STR environment 3.167 -# variable to make it easier to do network specific configuration. 3.168 -# 3.169 -# ssid: SSID (mandatory); either as an ASCII string with double quotation or 3.170 -# as hex string; network name 3.171 -# 3.172 -# scan_ssid: 3.173 -# 0 = do not scan this SSID with specific Probe Request frames (default) 3.174 -# 1 = scan with SSID-specific Probe Request frames (this can be used to 3.175 -# find APs that do not accept broadcast SSID or use multiple SSIDs; 3.176 -# this will add latency to scanning, so enable this only when needed) 3.177 -# 3.178 -# bssid: BSSID (optional); if set, this network block is used only when 3.179 -# associating with the AP using the configured BSSID 3.180 -# 3.181 -# priority: priority group (integer) 3.182 -# By default, all networks will get same priority group (0). If some of the 3.183 -# networks are more desirable, this field can be used to change the order in 3.184 -# which wpa_supplicant goes through the networks when selecting a BSS. The 3.185 -# priority groups will be iterated in decreasing priority (i.e., the larger the 3.186 -# priority value, the sooner the network is matched against the scan results). 3.187 -# Within each priority group, networks will be selected based on security 3.188 -# policy, signal strength, etc. 3.189 -# Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not 3.190 -# using this priority to select the order for scanning. Instead, they try the 3.191 -# networks in the order that used in the configuration file. 3.192 -# 3.193 -# mode: IEEE 802.11 operation mode 3.194 -# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default) 3.195 -# 1 = IBSS (ad-hoc, peer-to-peer) 3.196 -# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) 3.197 -# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has 3.198 -# to be set to 2 for IBSS. WPA-None requires following network block options: 3.199 -# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not 3.200 -# both), and psk must also be set. 3.201 -# 3.202 -# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g., 3.203 -# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial 3.204 -# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode. 3.205 -# In addition, this value is only used by the station that creates the IBSS. If 3.206 -# an IBSS network with the configured SSID is already present, the frequency of 3.207 -# the network will be used instead of this configured value. 3.208 -# 3.209 -# proto: list of accepted protocols 3.210 -# WPA = WPA/IEEE 802.11i/D3.0 3.211 -# RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN) 3.212 -# If not set, this defaults to: WPA RSN 3.213 -# 3.214 -# key_mgmt: list of accepted authenticated key management protocols 3.215 -# WPA-PSK = WPA pre-shared key (this requires 'psk' field) 3.216 -# WPA-EAP = WPA using EAP authentication (this can use an external 3.217 -# program, e.g., Xsupplicant, for IEEE 802.1X EAP Authentication 3.218 -# IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically 3.219 -# generated WEP keys 3.220 -# NONE = WPA is not used; plaintext or static WEP could be used 3.221 -# If not set, this defaults to: WPA-PSK WPA-EAP 3.222 -# 3.223 -# auth_alg: list of allowed IEEE 802.11 authentication algorithms 3.224 -# OPEN = Open System authentication (required for WPA/WPA2) 3.225 -# SHARED = Shared Key authentication (requires static WEP keys) 3.226 -# LEAP = LEAP/Network EAP (only used with LEAP) 3.227 -# If not set, automatic selection is used (Open System with LEAP enabled if 3.228 -# LEAP is allowed as one of the EAP methods). 3.229 -# 3.230 -# pairwise: list of accepted pairwise (unicast) ciphers for WPA 3.231 -# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 3.232 -# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 3.233 -# NONE = Use only Group Keys (deprecated, should not be included if APs support 3.234 -# pairwise keys) 3.235 -# If not set, this defaults to: CCMP TKIP 3.236 -# 3.237 -# group: list of accepted group (broadcast/multicast) ciphers for WPA 3.238 -# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 3.239 -# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 3.240 -# WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key 3.241 -# WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11] 3.242 -# If not set, this defaults to: CCMP TKIP WEP104 WEP40 3.243 -# 3.244 -# psk: WPA preshared key; 256-bit pre-shared key 3.245 -# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e., 3.246 -# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be 3.247 -# generated using the passphrase and SSID). ASCII passphrase must be between 3.248 -# 8 and 63 characters (inclusive). 3.249 -# This field is not needed, if WPA-EAP is used. 3.250 -# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys 3.251 -# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant 3.252 -# startup and reconfiguration time can be optimized by generating the PSK only 3.253 -# only when the passphrase or SSID has actually changed. 3.254 -# 3.255 -# eapol_flags: IEEE 802.1X/EAPOL options (bit field) 3.256 -# Dynamic WEP key required for non-WPA mode 3.257 -# bit0 (1): require dynamically generated unicast WEP key 3.258 -# bit1 (2): require dynamically generated broadcast WEP key 3.259 -# (3 = require both keys; default) 3.260 -# Note: When using wired authentication, eapol_flags must be set to 0 for the 3.261 -# authentication to be completed successfully. 3.262 -# 3.263 -# mixed_cell: This option can be used to configure whether so called mixed 3.264 -# cells, i.e., networks that use both plaintext and encryption in the same 3.265 -# SSID, are allowed when selecting a BSS form scan results. 3.266 -# 0 = disabled (default) 3.267 -# 1 = enabled 3.268 -# 3.269 -# proactive_key_caching: 3.270 -# Enable/disable opportunistic PMKSA caching for WPA2. 3.271 -# 0 = disabled (default) 3.272 -# 1 = enabled 3.273 -# 3.274 -# wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or 3.275 -# hex without quotation, e.g., 0102030405) 3.276 -# wep_tx_keyidx: Default WEP key index (TX) (0..3) 3.277 -# 3.278 -# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is 3.279 -# allowed. This is only used with RSN/WPA2. 3.280 -# 0 = disabled (default) 3.281 -# 1 = enabled 3.282 -#peerkey=1 3.283 -# 3.284 -# Following fields are only used with internal EAP implementation. 3.285 -# eap: space-separated list of accepted EAP methods 3.286 -# MD5 = EAP-MD5 (unsecure and does not generate keying material -> 3.287 -# cannot be used with WPA; to be used as a Phase 2 method 3.288 -# with EAP-PEAP or EAP-TTLS) 3.289 -# MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used 3.290 -# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 3.291 -# OTP = EAP-OTP (cannot be used separately with WPA; to be used 3.292 -# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 3.293 -# GTC = EAP-GTC (cannot be used separately with WPA; to be used 3.294 -# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 3.295 -# TLS = EAP-TLS (client and server certificate) 3.296 -# PEAP = EAP-PEAP (with tunnelled EAP authentication) 3.297 -# TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2 3.298 -# authentication) 3.299 -# If not set, all compiled in methods are allowed. 3.300 -# 3.301 -# identity: Identity string for EAP 3.302 -# anonymous_identity: Anonymous identity string for EAP (to be used as the 3.303 -# unencrypted identity with EAP types that support different tunnelled 3.304 -# identity, e.g., EAP-TTLS) 3.305 -# password: Password string for EAP 3.306 -# ca_cert: File path to CA certificate file (PEM/DER). This file can have one 3.307 -# or more trusted CA certificates. If ca_cert and ca_path are not 3.308 -# included, server certificate will not be verified. This is insecure and 3.309 -# a trusted CA certificate should always be configured when using 3.310 -# EAP-TLS/TTLS/PEAP. Full path should be used since working directory may 3.311 -# change when wpa_supplicant is run in the background. 3.312 -# On Windows, trusted CA certificates can be loaded from the system 3.313 -# certificate store by setting this to cert_store://<name>, e.g., 3.314 -# ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT". 3.315 -# Note that when running wpa_supplicant as an application, the user 3.316 -# certificate store (My user account) is used, whereas computer store 3.317 -# (Computer account) is used when running wpasvc as a service. 3.318 -# ca_path: Directory path for CA certificate files (PEM). This path may 3.319 -# contain multiple CA certificates in OpenSSL format. Common use for this 3.320 -# is to point to system trusted CA list which is often installed into 3.321 -# directory like /etc/ssl/certs. If configured, these certificates are 3.322 -# added to the list of trusted CAs. ca_cert may also be included in that 3.323 -# case, but it is not required. 3.324 -# client_cert: File path to client certificate file (PEM/DER) 3.325 -# Full path should be used since working directory may change when 3.326 -# wpa_supplicant is run in the background. 3.327 -# Alternatively, a named configuration blob can be used by setting this 3.328 -# to blob://<blob name>. 3.329 -# private_key: File path to client private key file (PEM/DER/PFX) 3.330 -# When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be 3.331 -# commented out. Both the private key and certificate will be read from 3.332 -# the PKCS#12 file in this case. Full path should be used since working 3.333 -# directory may change when wpa_supplicant is run in the background. 3.334 -# Windows certificate store can be used by leaving client_cert out and 3.335 -# configuring private_key in one of the following formats: 3.336 -# cert://substring_to_match 3.337 -# hash://certificate_thumbprint_in_hex 3.338 -# for example: private_key="hash://63093aa9c47f56ae88334c7b65a4" 3.339 -# Note that when running wpa_supplicant as an application, the user 3.340 -# certificate store (My user account) is used, whereas computer store 3.341 -# (Computer account) is used when running wpasvc as a service. 3.342 -# Alternatively, a named configuration blob can be used by setting this 3.343 -# to blob://<blob name>. 3.344 -# private_key_passwd: Password for private key file (if left out, this will be 3.345 -# asked through control interface) 3.346 -# dh_file: File path to DH/DSA parameters file (in PEM format) 3.347 -# This is an optional configuration file for setting parameters for an 3.348 -# ephemeral DH key exchange. In most cases, the default RSA 3.349 -# authentication does not use this configuration. However, it is possible 3.350 -# setup RSA to use ephemeral DH key exchange. In addition, ciphers with 3.351 -# DSA keys always use ephemeral DH keys. This can be used to achieve 3.352 -# forward secrecy. If the file is in DSA parameters format, it will be 3.353 -# automatically converted into DH params. 3.354 -# subject_match: Substring to be matched against the subject of the 3.355 -# authentication server certificate. If this string is set, the server 3.356 -# sertificate is only accepted if it contains this string in the subject. 3.357 -# The subject string is in following format: 3.358 -# /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com 3.359 -# altsubject_match: Semicolon separated string of entries to be matched against 3.360 -# the alternative subject name of the authentication server certificate. 3.361 -# If this string is set, the server sertificate is only accepted if it 3.362 -# contains one of the entries in an alternative subject name extension. 3.363 -# altSubjectName string is in following format: TYPE:VALUE 3.364 -# Example: EMAIL:server@example.com 3.365 -# Example: DNS:server.example.com;DNS:server2.example.com 3.366 -# Following types are supported: EMAIL, DNS, URI 3.367 -# phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters 3.368 -# (string with field-value pairs, e.g., "peapver=0" or 3.369 -# "peapver=1 peaplabel=1") 3.370 -# 'peapver' can be used to force which PEAP version (0 or 1) is used. 3.371 -# 'peaplabel=1' can be used to force new label, "client PEAP encryption", 3.372 -# to be used during key derivation when PEAPv1 or newer. Most existing 3.373 -# PEAPv1 implementation seem to be using the old label, "client EAP 3.374 -# encryption", and wpa_supplicant is now using that as the default value. 3.375 -# Some servers, e.g., Radiator, may require peaplabel=1 configuration to 3.376 -# interoperate with PEAPv1; see eap_testing.txt for more details. 3.377 -# 'peap_outer_success=0' can be used to terminate PEAP authentication on 3.378 -# tunneled EAP-Success. This is required with some RADIUS servers that 3.379 -# implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g., 3.380 -# Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode) 3.381 -# include_tls_length=1 can be used to force wpa_supplicant to include 3.382 -# TLS Message Length field in all TLS messages even if they are not 3.383 -# fragmented. 3.384 -# sim_min_num_chal=3 can be used to configure EAP-SIM to require three 3.385 -# challenges (by default, it accepts 2 or 3) 3.386 -# phase2: Phase2 (inner authentication with TLS tunnel) parameters 3.387 -# (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or 3.388 -# "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS) 3.389 -# Following certificate/private key fields are used in inner Phase2 3.390 -# authentication when using EAP-TTLS or EAP-PEAP. 3.391 -# ca_cert2: File path to CA certificate file. This file can have one or more 3.392 -# trusted CA certificates. If ca_cert2 and ca_path2 are not included, 3.393 -# server certificate will not be verified. This is insecure and a trusted 3.394 -# CA certificate should always be configured. 3.395 -# ca_path2: Directory path for CA certificate files (PEM) 3.396 -# client_cert2: File path to client certificate file 3.397 -# private_key2: File path to client private key file 3.398 -# private_key2_passwd: Password for private key file 3.399 -# dh_file2: File path to DH/DSA parameters file (in PEM format) 3.400 -# subject_match2: Substring to be matched against the subject of the 3.401 -# authentication server certificate. 3.402 -# altsubject_match2: Substring to be matched against the alternative subject 3.403 -# name of the authentication server certificate. 3.404 -# 3.405 -# fragment_size: Maximum EAP fragment size in bytes (default 1398). 3.406 -# This value limits the fragment size for EAP methods that support 3.407 -# fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set 3.408 -# small enough to make the EAP messages fit in MTU of the network 3.409 -# interface used for EAPOL. The default value is suitable for most 3.410 -# cases. 3.411 -# 3.412 -# EAP-PSK variables: 3.413 -# eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format 3.414 -# nai: user NAI 3.415 -# 3.416 -# EAP-PAX variables: 3.417 -# eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format 3.418 -# 3.419 -# EAP-SAKE variables: 3.420 -# eappsk: 32-byte (256-bit, 64 hex digits) pre-shared key in hex format 3.421 -# (this is concatenation of Root-Secret-A and Root-Secret-B) 3.422 -# nai: user NAI (PEERID) 3.423 -# 3.424 -# EAP-GPSK variables: 3.425 -# eappsk: Pre-shared key in hex format (at least 128 bits, i.e., 32 hex digits) 3.426 -# nai: user NAI (ID_Client) 3.427 -# 3.428 -# EAP-FAST variables: 3.429 -# pac_file: File path for the PAC entries. wpa_supplicant will need to be able 3.430 -# to create this file and write updates to it when PAC is being 3.431 -# provisioned or refreshed. Full path to the file should be used since 3.432 -# working directory may change when wpa_supplicant is run in the 3.433 -# background. Alternatively, a named configuration blob can be used by 3.434 -# setting this to blob://<blob name> 3.435 -# phase1: fast_provisioning=1 option enables in-line provisioning of EAP-FAST 3.436 -# credentials (PAC) 3.437 -# 3.438 -# wpa_supplicant supports number of "EAP workarounds" to work around 3.439 -# interoperability issues with incorrectly behaving authentication servers. 3.440 -# These are enabled by default because some of the issues are present in large 3.441 -# number of authentication servers. Strict EAP conformance mode can be 3.442 -# configured by disabling workarounds with eap_workaround=0. 3.443 - 3.444 -# Example blocks: 3.445 - 3.446 -# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers 3.447 -#network={ 3.448 -# ssid="simple" 3.449 -# psk="very secret passphrase" 3.450 -# priority=5 3.451 -#} 3.452 - 3.453 -# Same as previous, but request SSID-specific scanning (for APs that reject 3.454 -# broadcast SSID) 3.455 -#network={ 3.456 -# ssid="second ssid" 3.457 -# scan_ssid=1 3.458 -# psk="very secret passphrase" 3.459 -# priority=2 3.460 -#} 3.461 - 3.462 -# Only WPA-PSK is used. Any valid cipher combination is accepted. 3.463 -#network={ 3.464 -# ssid="example" 3.465 -# proto=WPA 3.466 -# key_mgmt=WPA-PSK 3.467 -# pairwise=CCMP TKIP 3.468 -# group=CCMP TKIP WEP104 WEP40 3.469 -# psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 3.470 -# priority=2 3.471 -#} 3.472 - 3.473 -# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104 3.474 -# or WEP40 as the group cipher will not be accepted. 3.475 -#network={ 3.476 -# ssid="example" 3.477 -# proto=RSN 3.478 -# key_mgmt=WPA-EAP 3.479 -# pairwise=CCMP TKIP 3.480 -# group=CCMP TKIP 3.481 -# eap=TLS 3.482 -# identity="user@example.com" 3.483 -# ca_cert="/etc/cert/ca.pem" 3.484 -# client_cert="/etc/cert/user.pem" 3.485 -# private_key="/etc/cert/user.prv" 3.486 -# private_key_passwd="password" 3.487 -# priority=1 3.488 -#} 3.489 - 3.490 -# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel 3.491 -# (e.g., Radiator) 3.492 -#network={ 3.493 -# ssid="example" 3.494 -# key_mgmt=WPA-EAP 3.495 -# eap=PEAP 3.496 -# identity="user@example.com" 3.497 -# password="foobar" 3.498 -# ca_cert="/etc/cert/ca.pem" 3.499 -# phase1="peaplabel=1" 3.500 -# phase2="auth=MSCHAPV2" 3.501 -# priority=10 3.502 -#} 3.503 - 3.504 -# EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the 3.505 -# unencrypted use. Real identity is sent only within an encrypted TLS tunnel. 3.506 -#network={ 3.507 -# ssid="example" 3.508 -# key_mgmt=WPA-EAP 3.509 -# eap=TTLS 3.510 -# identity="user@example.com" 3.511 -# anonymous_identity="anonymous@example.com" 3.512 -# password="foobar" 3.513 -# ca_cert="/etc/cert/ca.pem" 3.514 -# priority=2 3.515 -#} 3.516 - 3.517 -# EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted 3.518 -# use. Real identity is sent only within an encrypted TLS tunnel. 3.519 -#network={ 3.520 -# ssid="example" 3.521 -# key_mgmt=WPA-EAP 3.522 -# eap=TTLS 3.523 -# identity="user@example.com" 3.524 -# anonymous_identity="anonymous@example.com" 3.525 -# password="foobar" 3.526 -# ca_cert="/etc/cert/ca.pem" 3.527 -# phase2="auth=MSCHAPV2" 3.528 -#} 3.529 - 3.530 -# WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner 3.531 -# authentication. 3.532 -#network={ 3.533 -# ssid="example" 3.534 -# key_mgmt=WPA-EAP 3.535 -# eap=TTLS 3.536 - # Phase1 / outer authentication 3.537 -# anonymous_identity="anonymous@example.com" 3.538 -# ca_cert="/etc/cert/ca.pem" 3.539 - # Phase 2 / inner authentication 3.540 -# phase2="autheap=TLS" 3.541 -# ca_cert2="/etc/cert/ca2.pem" 3.542 -# client_cert2="/etc/cer/user.pem" 3.543 -# private_key2="/etc/cer/user.prv" 3.544 -# private_key2_passwd="password" 3.545 -# priority=2 3.546 -#} 3.547 - 3.548 -# Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and 3.549 -# group cipher. 3.550 -#network={ 3.551 -# ssid="example" 3.552 -# bssid=00:11:22:33:44:55 3.553 -# proto=WPA RSN 3.554 -# key_mgmt=WPA-PSK WPA-EAP 3.555 -# pairwise=CCMP 3.556 -# group=CCMP 3.557 -# psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 3.558 -#} 3.559 - 3.560 -# Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP 3.561 -# and all valid ciphers. 3.562 -#network={ 3.563 -# ssid=00010203 3.564 -# psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f 3.565 -#} 3.566 - 3.567 - 3.568 -# EAP-SIM with a GSM SIM or USIM 3.569 -#network={ 3.570 -# ssid="eap-sim-test" 3.571 -# key_mgmt=WPA-EAP 3.572 -# eap=SIM 3.573 -# pin="1234" 3.574 -# pcsc="" 3.575 -#} 3.576 - 3.577 - 3.578 -# EAP-PSK 3.579 -#network={ 3.580 -# ssid="eap-psk-test" 3.581 -# key_mgmt=WPA-EAP 3.582 -# eap=PSK 3.583 -# identity="eap_psk_user" 3.584 -# eappsk=06b4be19da289f475aa46a33cb793029 3.585 -# nai="eap_psk_user@example.com" 3.586 -#} 3.587 - 3.588 - 3.589 -# IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using 3.590 -# EAP-TLS for authentication and key generation; require both unicast and 3.591 -# broadcast WEP keys. 3.592 -#network={ 3.593 -# ssid="1x-test" 3.594 -# key_mgmt=IEEE8021X 3.595 -# eap=TLS 3.596 -# identity="user@example.com" 3.597 -# ca_cert="/etc/cert/ca.pem" 3.598 -# client_cert="/etc/cert/user.pem" 3.599 -# private_key="/etc/cert/user.prv" 3.600 -# private_key_passwd="password" 3.601 -# eapol_flags=3 3.602 -#} 3.603 - 3.604 - 3.605 -# LEAP with dynamic WEP keys 3.606 -#network={ 3.607 -# ssid="leap-example" 3.608 -# key_mgmt=IEEE8021X 3.609 -# eap=LEAP 3.610 -# identity="user" 3.611 -# password="foobar" 3.612 -#} 3.613 - 3.614 -# EAP-FAST with WPA (WPA or WPA2) 3.615 -#network={ 3.616 -# ssid="eap-fast-test" 3.617 -# key_mgmt=WPA-EAP 3.618 -# eap=FAST 3.619 -# anonymous_identity="FAST-000102030405" 3.620 -# identity="username" 3.621 -# password="password" 3.622 -# phase1="fast_provisioning=1" 3.623 -# pac_file="/etc/wpa_supplicant.eap-fast-pac" 3.624 -#} 3.625 - 3.626 -#network={ 3.627 -# ssid="eap-fast-test" 3.628 -# key_mgmt=WPA-EAP 3.629 -# eap=FAST 3.630 -# anonymous_identity="FAST-000102030405" 3.631 -# identity="username" 3.632 -# password="password" 3.633 -# phase1="fast_provisioning=1" 3.634 -# pac_file="blob://eap-fast-pac" 3.635 -#} 3.636 - 3.637 -# Plaintext connection (no WPA, no IEEE 802.1X) 3.638 -#network={ 3.639 -# ssid="plaintext-test" 3.640 -# key_mgmt=NONE 3.641 -#} 3.642 - 3.643 - 3.644 -# Shared WEP key connection (no WPA, no IEEE 802.1X) 3.645 -#network={ 3.646 -# ssid="static-wep-test" 3.647 -# key_mgmt=NONE 3.648 -# wep_key0="abcde" 3.649 -# wep_key1=0102030405 3.650 -# wep_key2="1234567890123" 3.651 -# wep_tx_keyidx=0 3.652 -# priority=5 3.653 -#} 3.654 - 3.655 - 3.656 -# Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key 3.657 -# IEEE 802.11 authentication 3.658 -#network={ 3.659 -# ssid="static-wep-test2" 3.660 -# key_mgmt=NONE 3.661 -# wep_key0="abcde" 3.662 -# wep_key1=0102030405 3.663 -# wep_key2="1234567890123" 3.664 -# wep_tx_keyidx=0 3.665 -# priority=5 3.666 -# auth_alg=SHARED 3.667 -#} 3.668 - 3.669 - 3.670 -# IBSS/ad-hoc network with WPA-None/TKIP. 3.671 -#network={ 3.672 -# ssid="test adhoc" 3.673 -# mode=1 3.674 -# frequency=2412 3.675 -# proto=WPA 3.676 -# key_mgmt=WPA-NONE 3.677 -# pairwise=NONE 3.678 -# group=TKIP 3.679 -# psk="secret passphrase" 3.680 -#} 3.681 - 3.682 - 3.683 -# Catch all example that allows more or less all configuration modes 3.684 -#network={ 3.685 -# ssid="example" 3.686 -# scan_ssid=1 3.687 -# key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE 3.688 -# pairwise=CCMP TKIP 3.689 -# group=CCMP TKIP WEP104 WEP40 3.690 -# psk="very secret passphrase" 3.691 -# eap=TTLS PEAP TLS 3.692 -# identity="user@example.com" 3.693 -# password="foobar" 3.694 -# ca_cert="/etc/cert/ca.pem" 3.695 -# client_cert="/etc/cert/user.pem" 3.696 -# private_key="/etc/cert/user.prv" 3.697 -# private_key_passwd="password" 3.698 -# phase1="peaplabel=0" 3.699 -#} 3.700 - 3.701 -# Example of EAP-TLS with smartcard (openssl engine) 3.702 -#network={ 3.703 -# ssid="example" 3.704 -# key_mgmt=WPA-EAP 3.705 -# eap=TLS 3.706 -# proto=RSN 3.707 -# pairwise=CCMP TKIP 3.708 -# group=CCMP TKIP 3.709 -# identity="user@example.com" 3.710 -# ca_cert="/etc/cert/ca.pem" 3.711 -# client_cert="/etc/cert/user.pem" 3.712 -# 3.713 -# engine=1 3.714 - 3.715 - # The engine configured here must be available. Look at 3.716 - # OpenSSL engine support in the global section. 3.717 - # The key available through the engine must be the private key 3.718 - # matching the client certificate configured above. 3.719 - 3.720 - # use the opensc engine 3.721 - #engine_id="opensc" 3.722 - #key_id="45" 3.723 - 3.724 - # use the pkcs11 engine 3.725 -# engine_id="pkcs11" 3.726 -# key_id="id_45" 3.727 -# 3.728 - # Optional PIN configuration; this can be left out and PIN will be 3.729 - # asked through the control interface 3.730 -# pin="1234" 3.731 -#} 3.732 - 3.733 -# Example configuration showing how to use an inlined blob as a CA certificate 3.734 -# data instead of using external file 3.735 -#network={ 3.736 -# ssid="example" 3.737 -# key_mgmt=WPA-EAP 3.738 -# eap=TTLS 3.739 -# identity="user@example.com" 3.740 -# anonymous_identity="anonymous@example.com" 3.741 -# password="foobar" 3.742 -# ca_cert="blob://exampleblob" 3.743 -# priority=20 3.744 -#} 3.745 - 3.746 -#blob-base64-exampleblob={ 3.747 -#SGVsbG8gV29ybGQhCg== 3.748 -#} 3.749 - 3.750 - 3.751 -# Wildcard match for SSID (plaintext APs only). This example select any 3.752 -# open AP regardless of its SSID. 3.753 -network={ 3.754 - key_mgmt=NONE 3.755 -} 3.756 - 3.757 -
4.1 --- a/firefox/rootfs/usr/share/applications/system-doc.desktop Tue May 31 00:45:49 2011 +0200 4.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 4.3 @@ -1,8 +0,0 @@ 4.4 -[Desktop Entry] 4.5 -Name=System Doc 4.6 -Name[fr]=Doc du système 4.7 -Name[pt]=Documentação do Sistema 4.8 -Exec=browser file:///usr/share/doc/slitaz/index.html 4.9 -Icon=slitaz-doc.png 4.10 -Type=Application 4.11 -Categories=Documentation;