Age | Commit message (Collapse) | Author | Files | Lines |
|
(This used to be commit c1e115964b671802a4af5beab3ad3222ee17b9c0)
|
|
Michael
(This used to be commit f7db445c828c0eef2c08b538bd07d485dc248689)
|
|
(This used to be commit 9e39ac1cc31d48db968e79c4698901e079007ff7)
|
|
Michael
(This used to be commit f8c0710165ee1ede46d7ed34daa5564d20d3f069)
|
|
Guenther
(This used to be commit d077ef64cd1d9bbaeb936566c2c70da508de829f)
|
|
cases.
Jeremy.
(This used to be commit 818fbc9889af8c9fb6e7978e8ed2269a78f14404)
|
|
Introduced by me in the strlcpy cleanup. Ensure the
loaded password doesn't contain the '\n' at the end.
Jeremy.
(This used to be commit 41984743d9e89b6568119832c35ee4c0024e43a2)
|
|
Jeremy.
(This used to be commit 7a724d78e11f016f154c0029dc394ce133f41110)
|
|
Karolin
(This used to be commit d99a31848bd2172c15500dd61ce30fef963c1ac6)
|
|
SAFE_FREE. Use #define constants not arbitrary numbers. Stevef
please check. Karolyn, once Steve has checked please pull for
3.2-stable.
Jeremy.
(This used to be commit cc23f91d639db61903bf8b6c9fa46ec9c1f44178)
|
|
(This used to be commit a51cb3c1a9549d74c1e5cf05bc43b955af1a25b7)
|
|
(This used to be commit 831a09ae25e98eacc0b0be5390d3ac3aa671a8a5)
|
|
(This used to be commit 4244be792eeb69e883a1ece013b62fe6941086f2)
|
|
(This used to be commit b294b2055a422e1af59e3b6843b84750b6786d99)
|
|
There were a couple of places where we weren't checking for
authentication correctly. This chance fixes those places and properly
supports Kerberos where available.
(This used to be commit 8eff35bc4acc13807c895af43b52db79ee195cb5)
|
|
To summarize the changes, the patches remove the old (probably non-
working) Kerberos support code which is unnecessary with CUPS 1.3
and adds some checks on the NT status we get back to see whether
the connection error is related to authentication. If so, we send
the ATTR: message to tell CUPS we need a username and password and
return exit code 2 so cupsd will do the right thing.
AUTH_USERNAME, AUTH_PASSWORD, and KRB5CCNAME are set and supported
by CUPS 1.3. The new exit code is supported by CUPS 1.2.x and 1.3,
and it treated as a general failure in CUPS 1.1. The ATTR: message
is only supported by CUPS 1.3, while CUPS 1.2 will assume the
"username,password" value we are setting.
The current code only uses the AUTH_* env vars if they are set.
If not, we fall back to the previous behavior.
I really can't tell whether the Kerberos code that was in there
would work at all. It did not work for Mac OS X which is why
I dropped it.
(This used to be commit 8c12c5cea01d9b801fe80c2a87b8139c488a62a5)
|
|
(This used to be commit 99fc3283c4ecc791f5a242bd1983b4352ce3e6cf)
|
|
This reduces the dependency on cli_state
(This used to be commit 783afab9c891dd7bcb78895b2a639b6f3a0edf5b)
|
|
connect on port 139 with IPv6. Found by David Holder @ Erion.
Karolin please merge to 3.2-stable.
Jeremy.
(This used to be commit c003e66ff10b23bb30aef0071ba7a3ae9579174e)
|
|
This patch is the second patch to attempt to fix up some of the problems
with mounting subdirectories of shares. The earlier patch didn't handle
this correctly when POSIX extensions were enabled. This one does.
This is a bit of a confusing area since the different components of
a service string have different rules:
1) hostname: no '/' (slash) or '\' (backslash) is allowed to be
embedded within the string
2) sharename: same rules as hostname
3) prefixpath: '\' *is* allowed to be embedded in a path component,
iff POSIX extensions are enabled. Otherwise, neither
character is allowed.
The idea here is to allow either character to act as a delimiter when we
know that the character can't be anything but a delimiter (namely
everywhere up to the start of the prefixpath). The patch will convert
any '\' unconditionally to '/' in the UNC portion of the string.
However, inside the prefixpath, we can't make assumptions about what
constitutes a delimiter because POSIX allows for embedded '\'
characters. So there we don't attempt to do any conversion, and pass the
prefixpath to the kernel as is. Once the kernel determines whether POSIX
extensions are enabled, it can then convert the path if needed and it's
able to do so. A patch to handle this has already been committed to the
cifs-2.6 git tree.
This patch also fixes an annoyance. When you mount a subdir of a share,
mount.cifs munges the device string so that you can't tell what the
prefixpath is. So if I mount:
//server/share/p1/p2/p3
..then /proc/mounts and mtab will show only:
//server/share
Finally, it also tries to apply some consistent rules to the uppercasing
of strings.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
(This used to be commit e03d1dfdb80333c071b600245eb749ef5664aa22)
|
|
(This used to be commit 8dd6458049d1b9d6849730ac19c39b049a68f302)
|
|
(This used to be commit 3fc85d22590550f0539215d020e4411bf5b14363)
|
|
dirmask is always set here, we've dereferenced it before anyway
(This used to be commit e6787aa133a1b241987319486c3bc46ac6ad41af)
|
|
finfo1==NULL just does not happen in current code
(This used to be commit 9ea0078c3151984a901c9bba559ae2bd7959e077)
|
|
Guenther
(This used to be commit 1121633652ffb77dce8df9cc91b7dfc2d55fd348)
|
|
Derrell
(This used to be commit b7f34e7ef2907b498a0645ce68f2773ed7d60cdc)
|
|
I did not do any scientific tests, but the dummy test on my laptop against a
w2k3 vmware shows that in this specific situation going beyond 512k seems not
to gain anything anymore.
smb: \> iosize 64512
iosize is now 64512
smb: \> lcd /dev
smb: \> get random null
getting file \random of size 104857600 as null (33453,1 kb/s) (average 19718,5 kb/s)
smb: \> get random null
getting file \random of size 104857600 as null (34236,0 kb/s) (average 20509,1 kb/s)
smb: \> iosize 524288
iosize is now 524288
smb: \> get random null
getting file \random of size 104857600 as null (49042,1 kb/s) (average 22521,9 kb/s)
smb: \> get random null
getting file \random of size 104857600 as null (49420,8 kb/s) (average 23432,9 kb/s)
smb: \> iosize 1048576
iosize is now 1048576
smb: \> get random null
getting file \random of size 104857600 as null (49420,8 kb/s) (average 24284,2 kb/s)
smb: \> get random null
getting file \random of size 104857600 as null (49136,3 kb/s) (average 25076,9 kb/s)
(This used to be commit 1bcfef6a9093aa873550a263dc142c8a3f5edffd)
|
|
(This used to be commit e602f06cbba852a7eacd15b2511ef2571a95cc80)
|
|
This is the big (and potentially controversial) one. It took a phone call to
explain to metze what is going on inside cli_pull_read_done, but I would really
like everybody to understand this function. It is a very good and reasonably
complex example of async programming. If we want more asynchronism in s3, this
is what we will have to deal with :-)
Make use of it in the smbclient "get" command.
Volker
(This used to be commit 76f9b360ee1d973630d82d401eeddce858189301)
|
|
This reverts commit 844a163458c7585e4306a21ffdae5d08e03d6e4d.
(This used to be commit 5ab1cfda500de07ff3c712442ab2fc74eecc8886)
|
|
This reverts commit 9a966e5593ae4474014aec5d8c68c489ac8ce0c9.
(This used to be commit 413695e8d0d8232a9c35e693f9a4a8009418ede4)
|
|
(This used to be commit 9a966e5593ae4474014aec5d8c68c489ac8ce0c9)
|
|
Karolin
(This used to be commit 5fbd98f7065268ae134108310119078ad8f62322)
|
|
This is the big (and potentially controversial) one. It took a phone call to
explain to metze what is going on inside cli_pull_read_done, but I would really
like everybody to understand this function. It is a very good and reasonably
complex example of async programming. If we want more asynchronism in s3, this
is what we will have to deal with :-)
Make use of it in the smbclient "get" command.
Volker
(This used to be commit 844a163458c7585e4306a21ffdae5d08e03d6e4d)
|
|
(This used to be commit d32066eaef1d09ec41fd5365e18eacd93e485d53)
|
|
Thanks to Walter Franzini
(This used to be commit 19de47fef1b35c47885acc40760a232e4643079c)
|
|
(This used to be commit ce57d388251063c22f89680e9d1c2129d9879975)
|
|
(This used to be commit a1d07469236c06b65f14a59a27d7f7abcb106b5e)
|
|
This reverts commit 6b1a118eaaab405eeef0cf3c0488a2747af562ba.
We found that this patch does not play well with currently released cifs.ko
code, so after discussions with Jeff Layton and Steve french we decided it
is best to back it off and re-think a better approach. Jeff will send new
patches later, but for now it is better to just revert to the previous code
(This used to be commit c5b7d538ecfa93377ff20704633ac57dbf8dd530)
|
|
for 3.2.
Jeremy.
(This used to be commit 69aa0766203cb88b8b07e364f7148ade809f5ce6)
|
|
(This used to be commit ba771bd858602452a9e58c3aab1336f2ac8a25ef)
|
|
(This used to be commit 71d6580c837adcc2cddcdff561f6fb09701501ee)
|
|
(This used to be commit 21d126c56a633d2d72ffad08db7331ecc0ee3c0c)
|
|
(This used to be commit fd34ce437057bb34cdc37f4b066e424000d36789)
|
|
Jeremy.
(This used to be commit 3a1bcbfa7ca2b55265eb486e2b7c740e04775698)
|
|
Modeled after the Samba4 allinfo command
(This used to be commit 3fa0cf3fe5f819f6e76df6f7cef3bb4e1c307a52)
|
|
Here is a patch for userspace cifs.spnego handler that adds support for cifs.resolver
upcall used in DFS code.
Any comments are appreciated.
#############################
Cifs upcall with key type cifs.resolver is used for resolving
server names in handling DFS refferals.
Signed-off-by: Igor Mammedov <niallain@gmail.com>
(This used to be commit dfc80b4f1c00c131ba8077432bfe79f22f63ccd1)
|
|
(This used to be commit 9c81125e6d3df49806e1c0b39409ffac8e3a0fd1)
|
|
(This used to be commit d3b91e494c824a65506ba1bc1cba5bba77000530)
|
|
Jeremy.
(This used to be commit ef1bbcdfb98da185c07005dd7810039f99f0685f)
|