krb5_des_decrypt() does not initialize the return value to 1, failure,
therefore it returns random success (0) values when ticket types of
DES-CBC-MD5 or DES-CBC-MD4 are used because we do not have checksum
functions for those types.
feeling like an idiot. the original test compared the size of the
ticket field in the ktc_token struct allocated by the app which might
be smaller than the size of the field defined in the library
Lowercase the cell name (from realm name) for which we are
requesting set/get token operations
Return the error code generated by the ktc_SetToken operation and
not one of the many Kerberos operations.
When processing pioctl() operations, properly perform the test of
the ticket size to the ktc.ticket field. The field is of fixed
size MAXKTCTICKETLEN and not some value which is adjusted based
upon the content of the message.
Corrections to the libadmin interface for the Windows Server Configurator
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
Use lanahelper.lib for the server configurator as well
In order to support the large ticket sizes produced by Microsoft
Active Directory and allow the use of raw Kerberos 5 tickets as tokens
increase the size of MAXKTCTICKETLEN and MAXKRB5TICKETLEN to 4096
from 344 and 1024 respectively.
Do not enforce the funky 8dot3 pattern matching rule that the first "."
is special when using long file names. (you must use "*.*" and not "*")
Instead only enforce it when performing 8dot3 searches.
Remove internally defined life_to_time. Instead rely on version
in rxkad
Use kvno = RXKAD_TKT_TYPE_KERBEROS_V5 when setting tokens. No longer
use krb524d.
Fix the assignment of the username and instance to place the instance
within the aclient.instance field instead of appended to the aclient.name
field.
Renumber and re-organize all of the String Table entries
to adhere to the rules specified for dynamically loading
them with the tools in WINNT/talocale. All numbers must
be sequential. Each block must begin on a mod 16 == 0
value.
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
Update resource constants to avoid conflicts
Make remove-vnop-denies-unlink-on-mtpt-20040325 more likely to work,
and don't forget to afs_PutFakeStat() while we're at it. After we
call afs_EvalFakeStat(), there's no way that mvstat can be 1 -- either
the object wasn't a mountpoint and it'll be mvstat 0, or EvalFakeStat
will evaluate it and it'll be mvstat 2.
apply patch to include more header and lib files.
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
Fix doug's patch. remote extraneous colons
Move (once again) the DependsOnXXX values to the right place.
(how did these end up back in NetworkProvider?)
Remove Rob's new way of installing services as it does not appear
to work properly.
Add in code to test the legitimacy of the upgrade to ensure we don't
try to upgrade an old IBM AFS version that isn't supported
Make sure that the only AFS in the PATH is ours and that we are only
in once.
Add the TransarcAFSDaemon entry into the Control\NetworkProviders::Order value
to support Integrated Login
Build service.exe and killer.exe with static libraries to avoid
run-time dependencies at install and uninstall time
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
Check both Client and Server for unsupported previous installation
The variable 'm_unique' is an afs_uint32 where the desired parameter
must be of type struct VLCallBack when attempting to call VL_GetAddrs.
I do not know how this code ever worked on any platform as the stack
was being overwritten.
This produced binary, vos.exe on windows, also generates massive
memory leaks. I do not think we care all that much because the
utility does not stay around all that long. However, the fact that
the API makes it so easy to lose memory is scary.
