krb5-wallet.git/client/keytab.c, branch debian/0.12-1 Unnamed repository; edit this file 'description' to name the repository. https://git.gnuabordo.com.br/debian/krb5-wallet.git/atom?h=debian%2F0.12-1 2010-08-26T01:01:37+00:00 Imported Upstream version 0.12 2010-08-26T01:01:37+00:00 Russ Allbery rra@stanford.edu 2010-08-26T01:01:37+00:00 urn:sha1:e91c0b93355b28617f7c0d756026856762ece242 Imported Upstream version 0.10 2010-02-22T01:45:55+00:00 Russ Allbery rra@stanford.edu 2010-02-22T01:45:55+00:00 urn:sha1:60210334fa3dbd5dd168199063c6ee850d750d0c Major coding style cleanup. Updated all shared code from my other 2008-04-24T02:02:49+00:00 Russ Allbery rra@stanford.edu 2008-04-24T02:02:49+00:00 urn:sha1:92ff7f21ad0b167f8d742a9d7b5f93704a57619c projects. The configure option requesting AFS kaserver support (and thus building kasetkey) is now --with-kaserver instead of --with-afs. If KRB5_CONFIG was explicitly set in the environment, don't use a different krb5-config based on --with-krb4 or --with-krb5. If krb5-config isn't executable, don't use it. This allows one to force library probing by setting KRB5_CONFIG to point to a nonexistent file. Sanity-check the results of krb5-config before proceeding and error out in configure if they don't work. Stop setting Stanford-specific compile-time defaults for the wallet server and port. When creating a srvtab based on a just-downloaded keytab, extract the 2008-02-07T00:46:54+00:00 Russ Allbery rra@stanford.edu 2008-02-07T00:46:54+00:00 urn:sha1:e733132938bc4fc74584b9a7c0f5441eb640e617 srvtab key before merging the keytab into an existing file. Otherwise, if the new keys had a lower kvno than the old keys (possible after deleting and recreating the object), the wrong key would be extracted for the srvtab. When downloading a keytab to a file that already exists, merge the new 2008-01-19T00:37:31+00:00 Russ Allbery rra@stanford.edu 2008-01-19T00:37:31+00:00 urn:sha1:aa57ab48cc9df24ab756b5651959b36a2d81cad3 keytab keys into that file rather than moving aside the old keytab and creating a new keytab with only the new keys. Also fix get handling in the client for all types other than keytabs. This isn't visible yet since the server doesn't yet support other types of objects. When getting a keytab with the client with no -f option, correctly 2008-01-17T00:21:00+00:00 Russ Allbery rra@stanford.edu 2008-01-17T00:21:00+00:00 urn:sha1:8dd5883b8497e4dcc7cf4f0577e45040c5f43430 write the keytab to standard output rather than dying with a cryptic error. The wallet client can now get the server, port, principal, and remctl 2008-01-05T00:01:54+00:00 Russ Allbery rra@stanford.edu 2008-01-05T00:01:54+00:00 urn:sha1:b10beb347238b153af8aa544fb276485b34e970e type from krb5.conf as well as from compile-time defaults and command-line options. Add comprehensive license information in LICENSE and update the copyright 2007-10-05T21:59:05+00:00 Russ Allbery rra@stanford.edu 2007-10-05T21:59:05+00:00 urn:sha1:500b0dfb2ec5a9cb561f6095f169275dee98e054 and license statements in all files. Make sure that some files that were missing copyright information now have them. Reference LICENSE rather than README in all notices. Fix the keytab attribute handling to call getattr and setattr instead of 2007-10-05T20:34:30+00:00 Russ Allbery rra@stanford.edu 2007-10-05T20:34:30+00:00 urn:sha1:64cae8e20ec8756a4c8503466a8754cecf417aa6 just attr to match the actual API. The wallet client now automatically sets the sync attribute on a keytab 2007-10-05T02:58:47+00:00 Russ Allbery rra@stanford.edu 2007-10-05T02:58:47+00:00 urn:sha1:dbd33500b645f9caaa6dbb7d18a3f4932b53847a object when get is called with the -S flag.