Age | Commit message (Collapse) | Author | Files | Lines |
|
(This used to be commit ec1b7000fd88c5a08e438c7033f60e49b9ec44a8)
|
|
(This used to be commit e164b5080ca966de4227277f7ac031bc96d056ad)
|
|
(This used to be commit 2d5fc5c7cf2086c396c853c13a3409bfac77d05c)
|
|
(This used to be commit 66e2787ab7db72fb654b995280b294738e77e50a)
|
|
Piping the output of smbmount back to autofs/automount was causing the
automount process to hang. Reason was that automount was depending
on the pipe to close to continue on, rather than detecting the child
signal. This occured with debug enabled and the daemon process was not
closing the stdout process. Disabling debuging avoids the problem.
Debugging is turned off in the cvs repository and a warning placed over
the debugging option.
(This used to be commit 329ceaee49fa0175f78873433bd942865309f633)
|
|
(This used to be commit 59f081069a58f6a070ed6016c06153d5e695da93)
|
|
(This used to be commit ba5919bcaefa792bae503c7ab19d4b7bbf9bb954)
|
|
Also some string length and sizeof(pointer) corrections.
(This used to be commit ce24191939b82985d09eabe945199f38b0fea486)
|
|
(This used to be commit b314430b2102e47529b093b1b98b5b6f3b6ea74f)
|
|
caching the password if it came from the command line or from the environment.
This completes the set and deals with the bloody nusance when reconnecting
a connection after we have gone daemon... Grrr...
Added code to clean up the mount point following a catastrophic failure
during reconnect. The smbmount daemon was exiting but leaving the mount
point in an unusable state. If smbmount must exit following a reconnect
failure, we "unmount" the mount point and clean up mnttab. Currently,
the unmount works, fixing some really ugly I/O errors and failure when
trying to remount. The cleanup on mnttab still has problems. This
is better than what it was and doesn't break anything that wasn't broken
before, so I'm committing this in even with the mnttab problem. Will
commit the fix to that when I figure out what is busted there...
-mhw-
(This used to be commit ad8389804cec6c6bf04601a1d7bb3fb7aa8c2274)
|
|
(This used to be commit 1041d53ec246debac0050bdc7e9a6cd72e9ecf49)
|
|
in smbmount.c
(This used to be commit 4b4a706213032ad49a0653e80721bac5f6284f90)
|
|
(This used to be commit dad5baef194b18c674c0d908a0e0714c0a1aefa4)
|
|
(This used to be commit 98ecb88704c3db26de8b548f4f1526f23401a161)
|
|
(This used to be commit 9ea91d89d2a1baa67f5143ecc08eb60c93213242)
|
|
No more ugly static library buffers and all functions take a destination
string length (especially unistrcpy was rather dangerous; we were only
saved by the fact that datagrams are limited in size).
(This used to be commit a1d39af1ce1d451b811dbd7c2ba391214851b87e)
|
|
(This used to be commit 6a437cfb33f24913e0c1f8484c0b08ef317e513b)
|
|
(This used to be commit 73db80f34183324845407b00f58462ff2d7b47ea)
|
|
as you need to make multiple enum dom users calls.
(This used to be commit b5396d3c6de4b8cb0e981bab10367e5838f78a53)
|
|
don't wait for responses :-)
(This used to be commit c1d65e906054297e42d6d177194d3b9ab16c7e35)
|
|
(This used to be commit d77de868588b6291353fa7a426b6e5da4b5f2c49)
|
|
(This used to be commit c5109ff782be8774db47a92b48ca6335ec8d6065)
|
|
under SID_NAME_ENUM 0x5 instead of 0x2 (Well-known group instead of
Domain Group) was making it impossible to view these groups from USRMGR.EXE.
(This used to be commit 3072044134eadbf46350b32c1ed0703681b0d590)
|
|
representation in the underlying database: removed this code.
for example, with the nt->unix mapping system (don't know about the ldap
one) if you want "Domain Admins" to appear you _must_ put it in the
domaingroup.map file.
the previous code was adding builtin aliases and well-known groups even
if they weren't in the domain maps. bad idea.
(This used to be commit 56469578a1af0fbcf6edddf94c498c7bbfb385c6)
|
|
prev_pdu_file_offset was not being re-initialised to zero.
(This used to be commit fcaa1214412f5a417a648d4da5c4332f75f59f57)
|
|
which is more appropriate.
(This used to be commit ac72fe1ab3d10f64a5945ccbd4ed3817e30f9f7b)
|
|
pwdb_sam_map_names() was using a "blank" static string instead of
a NULL pointer for nt names. NULL means over-ride, so the nt name
got left as "blank".
this causes nt clients to terminate with extreme prejudice.
(This used to be commit ddd350198202d6a1d2c715b3dce7db3a5d76a63a)
|
|
around anyway.
The real problem is, once again, the brokenness of pwdb_sam_map_names et al.
This time it is deciding to return blank NT usernames, which NT's redirector
objects to.
I'm currently working on improving the pwdb/mapping code, should be ready in a
couple of weeks.
(This used to be commit 30a085bf80982c619cd78aee9ad410ece5f88679)
|
|
(This used to be commit 9084b7e33dfe717bd8d5604ee71d137e3baef0f5)
|
|
get_myname.
(This used to be commit 9ab81caa065a0e08368fc9137d42ed810fd4b817)
|
|
to resolution of unix name to nt name being unnecessarily _inside_
another loop.
(This used to be commit d455c9d2c9f60289d78d0331228f5922152070bf)
|
|
(This used to be commit ed128c38a88746ec7822d598e72f0106a30a4af7)
|
|
(This used to be commit 62118e15fed8c9a7e13705842d0ae59669a2dd8f)
|
|
right place (forgot to subtract 0x18 header bytes)
(This used to be commit 5b9a7278da4a25ea217f914c8daae31238fa5cfe)
|
|
(This used to be commit f7dfa55a2e191ae780d399026bce48f68cda4bf0)
|
|
(This used to be commit f082f07e764c04b75b6880f852b80faec86f1b1c)
|
|
domain member, pdc, bdc.
(This used to be commit d95bb252f838b3612f5eba5d2b61d7b38b01f5ef)
|
|
to memset changes...
(This used to be commit 1cb8fcb33bb9e930d8f3cba4cc1ba5aa880c5f8e)
|
|
(This used to be commit ce1ae86cbd8dec18ff981d1fce05ed660e263f38)
|
|
(This used to be commit af83778abc5fae0df53ed1874181e33bc8de8d94)
|
|
unix_to_nt_time hack. Seems to me it's ignored anyway (dummy return
buffer?).
(This used to be commit 1e3873111faf352ef14a098eff250b505ab0b800)
|
|
endlessly repeating a network SAMLOGON (hoping it to change, hmmm...).
( Guess what I found in pwdb_init_sam...
unix_to_nt_time(&user->logon_time, (time_t)-1);
unix_to_nt_time(&user->logoff_time, (time_t)-1);
unix_to_nt_time(&user->kickoff_time, (time_t)-1);
... )
(This used to be commit e9c79c85e6d1352693ab13e907b07d4706975891)
|
|
(This used to be commit e1e3875057bed830fdc0aaa9c85f04a1479fd64a)
|
|
1) The earlier fix for the smbmount race conditions broke the PID
registration with smbfs. That fix has been backed out and
replaced by a signalling convention from the child smbmount
process back to the parent telling the parent when it is safe
to exit.
2) Fixing all of this uncovered a NASTY deadly embrace between smbmount,
smbmnt, and autofs. This was caused by the setsid call in the
daemon code. The smbmnt process no longer was registered as
"magic" because it was no longer in the autofs process group.
Many many kudos and thanks to H Peter Anvin for giving me the
clue to solving this agravating puzzle. The setsid was moved
down the where the child signals the parent and a warn left in
its place in the daemonize code.
3) Fixed (actually worked around with a BUTT UGLY HACK) a problem with
SMB_GET_MOUNTPID in smbumount.c. The smb_fs.h header file has
the parameter to this ioctl defined as a uid_t. Unfortunately
that's a 32 bit quantity under glibc and it's currently a 16 bit
quantity in kernel space. Undefined the macro and redefined
it with a parameter of __kernel_uid_t. That should keep us
out of trouble till I can have someone fix smb_fs.h in the
kernel sources...
(This used to be commit c5608093e48ed7fd3b7a1e2a4b1af7e4e59fc2f9)
|
|
also needed to use start index properly and generate next index.
both client and server code need to recognise error code 0x105
when there's not enough room to store all the users in one call.
sort this out another time.
(This used to be commit ad58cdfac6b85d9431216e32e532ad4d60f9c6dd)
|
|
fn decides whether to encrypt password or not.
(This used to be commit 6d14db6a6c101e86b3c62d5098a05d29ae4e9cd8)
|
|
(This used to be commit 14080a564a24f8f35cb8711b912c46f7243cd723)
|
|
(This used to be commit a022710f1e3996ecbe6bbe035e1df0bc4c050b34)
|
|
(This used to be commit 61c40982d6fde34729dc6850cf3372482392f4c9)
|
|
validation checks and also added capability to send plaintext passwords.
send "ntpasslen" of zero to do this. sending same plaintext password
for pass and ntpass arguments will result in previous behaviour of
encrypting password if server supports it.
(This used to be commit 17f4c5a785cf20901bcb76510e5ea9b0a6928115)
|