Changeset 1030

Timestamp:

04/20/06 11:01:42 (3 years ago)

Author:

tushar

Message:

Updated: starting-and-stopping-fusesmb-with-kdm

Files:

• trunk/starting-and-stopping-fusesmb-with-kdm.txt (modified) (10 diffs)
• trunk/wpa-service.txt (moved) (moved from trunk/wpa-service) (1 diff)

trunk/starting-and-stopping-fusesmb-with-kdm.txt

@@ -1 +1 @@
-AUTHOR: Stef Bon <stef at bononline dot nl>
-
-1-24
+4-15
-
-LICENSE: GNU Free Documentation License Version 1.2
-
- and PAM
+
-
-DESCRIPTION: 
@@ -11 +11 @@
-
-This is based on my hint 
- and PAM
+
-
-In this hint is described in general how scripts and commands are 
-
-
+
-
-
@@ -33 +32 @@
-1.2 Starting fusesmb.
-1.3 Stopping fusesmb.
-1.4 Storing credentials in personal configurationfile.
-
-
@@ -42 +40 @@
-Very new is FUSE. At this moment the FUSE package contains a kernelmodule, a library and utilities.
-Soon the module will be standard in the kernel. For more information see the website of course.
-
-Pam_script has the ability (from version 0.1.5) to get the password provided at login, and provide this via an evironmentvariable PAM_AUTHTOK to scripts. A script for fusesmb can write this value to the configurationfile of fusesmb (~/.smb/fusesmb.conf) to browse the network with the credentials provided at login. 
-
-warning:
-
-This looks a little bit like Single Sign On, but it isn't!! The credentials are stored in 
-a subdirectory of the homedir (~/.smb/fusesmb.conf), with enough security at runtime.
-But somebody can still find them being root, or with a LiveCD. The credentials are stored
-plaintext, no encryption!!
-
-So, this should never be used in an environment where you can't trust your users!
-
-
--------------------------------------
@@ -124 +110 @@
-
-userid=$1
-
+m 1-
-homedir=$(echo $userproperties | cut -d ":" -f 6);
-gidnr=$(echo $userproperties | cut -d ":" -f 4);
@@ -159 +145 @@
-application, like MC or vi.
-
+This configuration allows other users to enter the fusesmb filesystem. If you don't want this, you should remove 
+the "allow_other" flag.
+
-
-------------------------
@@ -174 +163 @@
-
-userid=$1
-
+m 1 -
-homedir=$(echo $userproperties | cut -d ":" -f 6);
-gidnr=$(echo $userproperties | cut -d ":" -f 4);
@@ -187 +176 @@
-    fi;
-
-    if [ -e $homedir/.smb/fusesmb.conf ]; then
-
-        rm -f $homedir/.smb/fusesmb.conf
-
-    fi;
-
-fi;
-
@@ -204 +187 @@
-
-
-------------------------------------------------------
-1.4 Storing credentials in personal configurationfile.
-------------------------------------------------------
-
-With files above you could already get a working sollution.
-To access the SMB servers where a username and a password are
-required, FuseSMB allows you to give credentials in the 
-~/.smb/fusesmb.conf file. Look for these and more options
-in the manpage of fusesmb.conf.
-
-With PAM and the module pam_script it is possible to use the
-credentials provided at login. In my network the sambaservers
-use the same credentials as my normal login  (via OPENLDAP).
-
-cat >> /etc/session.d/pam/onauth/fusesmb.sh << "EOF"
-#!/bin/bash
-
-retcode=0;
-
-userid=$1
-service=$2
-authtok=$3
-
-userproperties=$(getent passwd | grep -E "^$userid")
-homedir=$(echo $userproperties | cut -d ":" -f 6);
-gidnr=$(echo $userproperties | cut -d ":" -f 4);
-uidnr=$(echo $userproperties | cut -d ":" -f 3);
-
-if [ -d $homedir ]; then
-
-
-        if [ ! -d $homedir/.smb ]; then
-
-            mkdir -p $homedir/.smb
-            chown $uidnr:$gidnr $homedir/.smb
-            chmod 755 $homedir/.smb
-
-        fi
-
-        if [ -n "$authtok" ]; then
-
-            rm -f $homedir/.smb/fusesmb.conf
-
-            touch $homedir/.smb/fusesmb.conf
-            chown $uidnr:$gidnr $homedir/.smb/fusesmb.conf
-            chmod 600 $homedir/.smb/fusesmb.conf
-
-            echo "[global]" > $homedir/.smb/fusesmb.conf
-            echo "username = $userid" >> $homedir/.smb/fusesmb.conf
-            echo "password = $authtok" >> $homedir/.smb/fusesmb.conf
-
-        fi;
-
-fi;
-
-
-if [ $retcode -ne 0 ]; then
-    echo "An error with fusesmb ($retcode)."
-fi;
-
-exit $retcode
-EOF
-
-
-Notes:
-
-- The fusesmb script in the onauth directory overwrites any existing fusesmb.conf in the ~/.smb 
-directory. I do not have any simple sollution to do otherwise. One way to do that is the use of 
-a template. In this template the variables username and password get inserted with 'sed'.
-- this script is executed before(!) any script started by KDM. So when fusesmb starts, it reads 
-this new configuration file.
-
-
@@ -285 +197 @@
-[2006-01-30]
-  * fixed some typos
-
+
+
+

trunk/wpa-service.txt

@@ -5 +5 @@
-LICENSE: GNU Free Documentation License Version 2
-
-
-
+
-
-DESCRIPTION: