Changeset 860 for vendor/current/docs-xml/manpages-3
- Timestamp:
- May 12, 2014, 8:58:38 PM (11 years ago)
- Location:
- vendor/current/docs-xml/manpages-3
- Files:
-
- 1 added
- 4 edited
-
dbwrap_tool.1.xml (added)
-
idmap_ad.8.xml (modified) (1 diff)
-
ntlm_auth.1.xml (modified) (1 diff)
-
vfs_catia.8.xml (modified) (5 diffs)
-
vfs_crossrename.8.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/manpages-3/idmap_ad.8.xml
r740 r860 23 23 extensions. This module implements only the "idmap" 24 24 API, and is READONLY. Mappings must be provided in advance 25 by the administrator by adding the posixAccount/posixGroup 26 classes and relative attribute/value pairs to the user and 27 group objects in the AD.</para> 25 by the administrator by adding the uidNumber attributes for 26 users and gidNumber attributes for groups in the AD. Winbind 27 will only map users that have a uidNumber and whose primary 28 group have a gidNumber attribute set. It is however 29 recommended that all groups in use have gidNumber attributes 30 assigned, otherwise they are not working.</para> 28 31 29 32 <para> -
vendor/current/docs-xml/manpages-3/ntlm_auth.1.xml
r746 r860 161 161 <variablelist> 162 162 <varlistentry> 163 <term>Username</term> 164 165 <listitem><para>The username, expected to be in 166 Samba's <smbconfoption name="unix charset"/>. 167 </para> 168 169 <para><example>Username: bob</example></para> 170 <para><example>Username:: Ym9i</example></para> 171 </listitem></varlistentry> 172 173 <varlistentry> 174 <term>NT-Domain</term> 175 <listitem><para>The user's domain, expected to be in 176 Samba's <smbconfoption name="unix charset"/>. 177 </para> 178 179 <para><example>NT-Domain: WORKGROUP</example></para> 180 <para><example>NT-Domain:: V09SS0dST1VQ</example></para> 181 </listitem></varlistentry> 182 183 <varlistentry> 184 <term>Full-Username</term> 185 <listitem><para>The fully qualified username, expected to be in 186 Samba's <smbconfoption name="unix charset"/> and qualified with the 187 <smbconfoption name="winbind separator"/>. 188 </para> 189 190 <para><example>Full-Username: WORKGROUP\bob</example></para> 191 <para><example>Full-Username:: V09SS0dST1VQYm9i</example></para> 192 </listitem></varlistentry> 193 194 <varlistentry> 195 <term>LANMAN-Challenge</term> 196 197 <listitem><para>The 8 byte <command>LANMAN Challenge</command> value, 198 generated randomly by the server, or (in cases such as 199 MSCHAPv2) generated in some way by both the server and 200 the client. 201 </para> 202 <para><example>LANMAN-Challenge: 0102030405060708</example></para> 203 </listitem></varlistentry> 204 205 <varlistentry> 206 <term>LANMAN-Response</term> 207 208 <listitem><para>The 24 byte <command>LANMAN Response</command> value, 209 calculated from the user's password and the supplied 210 <command>LANMAN Challenge</command>. Typically, this 211 is provided over the network by a client wishing to authenticate. 212 </para> 213 <para><example>LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</example></para> 214 215 </listitem></varlistentry> 216 217 <varlistentry> 218 <term>NT-Response</term> 219 <listitem><para>The >= 24 byte <command>NT Response</command> 220 calculated from the user's password and the supplied 221 <command>LANMAN Challenge</command>. Typically, this is 222 provided over the network by a client wishing to authenticate. 223 </para> 224 <para><example>NT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</example></para> 225 226 </listitem></varlistentry> 227 228 <varlistentry> 229 <term>Password</term> 230 <listitem><para>The user's password. This would be 231 provided by a network client, if the helper is being 232 used in a legacy situation that exposes plaintext 233 passwords in this way. 234 </para> 235 <para><example>Password: samba2</example></para> 236 <para><example>Password:: c2FtYmEy</example></para> 237 238 </listitem></varlistentry> 239 240 <varlistentry> 241 <term>Request-User-Session-Key</term> 242 <listitem><para>Upon successful authenticaiton, return 243 the user session key associated with the login. 244 </para> 245 <para><example>Request-User-Session-Key: Yes</example></para> 246 247 </listitem></varlistentry> 248 249 <varlistentry> 250 <term>Request-LanMan-Session-Key</term> 251 <listitem><para>Upon successful authenticaiton, return 252 the LANMAN session key associated with the login. 253 </para> 254 <para><example>Request-LanMan-Session-Key: Yes</example></para> 255 256 </listitem></varlistentry> 257 258 <para><warning>Implementers should take care to base64 encode 259 any data (such as usernames/passwords) that may contain malicous user data, such as 260 a newline. They may also need to decode strings from 261 the helper, which likewise may have been base64 encoded.</warning></para> 262 </variablelist> 263 163 <term>Username</term> 164 <listitem><para>The username, expected to be in 165 Samba's <smbconfoption name="unix charset"/>. 166 </para> 167 <varlistentry> 168 <term>Examples:</term> 169 <para>Username: bob</para> 170 <para>Username:: Ym9i</para> 171 </varlistentry> 172 </listitem> 173 </varlistentry> 174 175 <varlistentry> 176 <term>NT-Domain</term> 177 <listitem><para>The user's domain, expected to be in 178 Samba's <smbconfoption name="unix charset"/>. 179 </para> 180 181 <varlistentry> 182 <term>Examples:</term> 183 <para>NT-Domain: WORKGROUP</para> 184 <para>NT-Domain:: V09SS0dST1VQ</para> 185 </varlistentry> 186 </listitem> 187 </varlistentry> 188 189 <varlistentry> 190 <term>Full-Username</term> 191 <listitem><para>The fully qualified username, expected to be 192 in Samba's <smbconfoption name="unix charset"/> and qualified 193 with the <smbconfoption name="winbind separator"/>.</para> 194 <varlistentry> 195 <term>Examples:</term> 196 <para>Full-Username: WORKGROUP\bob</para> 197 <para>Full-Username:: V09SS0dST1VQYm9i</para> 198 </varlistentry> 199 </listitem> 200 </varlistentry> 201 202 <varlistentry> 203 <term>LANMAN-Challenge</term> 204 <listitem><para>The 8 byte <command>LANMAN Challenge</command> 205 value, generated randomly by the server, or (in cases such 206 as MSCHAPv2) generated in some way by both the server and 207 the client.</para> 208 <varlistentry> 209 <term>Examples:</term> 210 <para>LANMAN-Challenge: 0102030405060708</para> 211 </varlistentry> 212 </listitem> 213 </varlistentry> 214 215 <varlistentry> 216 <term>LANMAN-Response</term> 217 <listitem><para>The 24 byte <command>LANMAN Response</command> value, 218 calculated from the user's password and the supplied 219 <command>LANMAN Challenge</command>. Typically, this 220 is provided over the network by a client wishing to authenticate. 221 </para> 222 <varlistentry> 223 <term>Examples:</term> 224 <para>LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718</para> 225 </varlistentry> 226 </listitem> 227 </varlistentry> 228 229 <varlistentry> 230 <term>NT-Response</term> 231 <listitem><para>The >= 24 byte <command>NT Response</command> 232 calculated from the user's password and the supplied 233 <command>LANMAN Challenge</command>. Typically, this is 234 provided over the network by a client wishing to authenticate. 235 </para> 236 <varlistentry> 237 <term>Examples:</term> 238 <para>NT-Response: 0102030405060708090A0B0C0D0E0F10111213141516171</para> 239 </varlistentry> 240 </listitem> 241 </varlistentry> 242 243 <varlistentry> 244 <term>Password</term> 245 <listitem><para>The user's password. This would be 246 provided by a network client, if the helper is being 247 used in a legacy situation that exposes plaintext 248 passwords in this way.</para> 249 <varlistentry> 250 <term>Examples:</term> 251 <para>Password: samba2</para> 252 <para>Password:: c2FtYmEy</para> 253 </varlistentry> 254 </listitem> 255 </varlistentry> 256 257 <varlistentry> 258 <term>Request-User-Session-Key</term> 259 <listitem><para>Upon successful authenticaiton, return 260 the user session key associated with the login.</para> 261 <varlistentry> 262 <term>Examples:</term> 263 <para>Request-User-Session-Key: Yes</para> 264 </varlistentry> 265 </listitem> 266 </varlistentry> 267 268 <varlistentry> 269 <term>Request-LanMan-Session-Key</term> 270 <listitem><para>Upon successful authenticaiton, return 271 the LANMAN session key associated with the login. 272 </para> 273 <varlistentry> 274 <term>Examples:</term> 275 <para>Request-LanMan-Session-Key: Yes</para> 276 </varlistentry> 277 </listitem> 278 </varlistentry> 279 280 </variablelist> 264 281 </listitem> 265 282 </varlistentry> 266 </variablelist> 267 </listitem> 283 </variablelist> 284 <warning><para>Implementers should take care to base64 encode 285 any data (such as usernames/passwords) that may contain malicous user data, such as 286 a newline. They may also need to decode strings from 287 the helper, which likewise may have been base64 encoded.</para></warning> 288 </listitem> 268 289 </varlistentry> 269 290 -
vendor/current/docs-xml/manpages-3/vfs_catia.8.xml
r740 r860 32 32 <para>The Catia CAD package commonly creates filenames that 33 33 use characters that are illegal in CIFS filenames. The 34 <command>vfs_catia</command> VFS module implements a fixedcharacter34 <command>vfs_catia</command> VFS module implements a character 35 35 mapping so that these files can be shared with CIFS clients. 36 36 </para> 37 37 38 38 <para>This module is stackable.</para> 39 40 <para>Up to samba version 3.4.x a fixed character mapping was used. 41 The invalid windows characters \ / : * ? " < > | and the blank 42 character were mapped in a hardcoded way. 43 </para> 44 45 <para>Starting with samba-3.5.0 a more flexible mapping was introduced. 46 The new parameter "catia:mappings" now specifies the mapping on a char by char 47 basis using the notation: unix hex char 0x.. : windows hex char 0x.. 48 Multiple character mappings are separated by a comma. 49 </para> 50 39 51 40 52 </refsect1> … … 44 56 <title>EXAMPLES</title> 45 57 58 <para>Samba versions up to 3.4.x:</para> 46 59 <para>Map Catia filenames on the [CAD] share:</para> 47 60 … … 52 65 </programlisting> 53 66 67 <para>Samba versions 3.5.0 and later:</para> 68 <para>Map Catia filenames on the [CAD] share:</para> 69 70 <programlisting> 71 <smbconfsection name="[CAD]"/> 72 <smbconfoption name="path">/data/cad</smbconfoption> 73 <smbconfoption name="vfs objects">catia</smbconfoption> 74 <smbconfoption name="catia:mappings">0x22:0xa8</smbconfoption> 75 </programlisting> 76 77 <para>To get the full formerly fixed mappings:</para> 78 <programlisting> 79 <smbconfsection name="[CAD]"/> 80 <smbconfoption name="path">/data/cad</smbconfoption> 81 <smbconfoption name="vfs objects">catia</smbconfoption> 82 <smbconfoption name="catia:mappings">0x22:0xa8,0x2a:0xa4,0x2f:0xf8,0x3a:0xf7,0x3c:0xab,0x3e:0xbb,0x3f:0xbf,0x5c:0xff,0x7c:0xa6,0x20:0xb1</smbconfoption> 83 </programlisting> 84 85 <para>Unix filename to be translated (Note that the path delimiter "/" is not used here): 86 </para> 87 <para>a\a:a*a?a"a<a>a|a a</para> 88 89 <para>Resulting windows filename:</para> 90 91 <para>aÿa÷a¤a¿a¨a«a»a¦a±a 92 </para> 93 94 <para>Note that the character mapping must work in BOTH directions 95 (unix -> windows and windows -> unix) to get unique and existing file names! 96 </para> 97 98 <para>A NOT working example:</para> 99 100 <programlisting> 101 <smbconfsection name="[CAD]"/> 102 <smbconfoption name="path">/data/cad</smbconfoption> 103 <smbconfoption name="vfs objects">catia</smbconfoption> 104 <smbconfoption name="catia:mappings">0x3a:0x5f</smbconfoption> 105 </programlisting> 106 107 <para>Here the colon ":" is mapped to the underscore "_".</para> 108 <para>Assuming a unix filename "a:should_work", which is well translated 109 to windows as "a_should_work".</para> 110 <para>BUT the reverse mapping from windows "a_should_work" to unix 111 will result in "a:should:work" - something like "file not found" 112 will be returned. 113 </para> 114 54 115 </refsect1> 55 116 … … 57 118 <title>VERSION</title> 58 119 59 <para>This man page is correct for version 3.0.25of the Samba suite.120 <para>This man page is correct for all versions up to 4.0.3 of the Samba suite. 60 121 </para> 61 122 </refsect1> … … 68 129 by the Samba Team as an Open Source project similar 69 130 to the way the Linux kernel is developed.</para> 131 <para>New version written by Guenter Kukkukk kukks@samba.org</para> 70 132 71 133 </refsect1> -
vendor/current/docs-xml/manpages-3/vfs_crossrename.8.xml
r740 r860 38 38 manual copy and delete operations. If the rename by copy is done by the 39 39 server this can be much more efficient. vfs_crossrename tries to do 40 this server-side cross-device rename operation. There are however 41 limitations that this module currently does not solve: 40 this server-side cross-device rename operation. 41 </para> 42 43 <para>There are however limitations that this module currently does not 44 solve:</para> 42 45 43 46 <variablelist> 44 47 <varlistentry> 45 the ACLs of files are not preserved48 <para>The ACLs of files are not preserved,</para> 46 49 </varlistentry> 47 50 <varlistentry> 48 meta data in EAs are not preserved51 <para>meta data in EAs are not preserved,</para> 49 52 </varlistentry> 50 53 <varlistentry> 51 renames of whole subdirectories cannot be done recursively,54 <para>renames of whole subdirectories cannot be done recursively, 52 55 in that case we still return STATUS_NOT_SAME_DEVICE and 53 let the client decide what to do 56 let the client decide what to do,</para> 54 57 </varlistentry> 55 58 <varlistentry> 56 rename operations of huge files can cause hangs on the59 <para>rename operations of huge files can cause hangs on the 57 60 client because clients expect a rename operation to 58 return fast 61 return fast.</para> 59 62 </varlistentry> 60 63 </variablelist> 61 </para>62 64 63 65 <para>This module is stackable.</para>
Note:
See TracChangeset
for help on using the changeset viewer.
