krb5-wallet.git/client, branch debian/0.10-1 Unnamed repository; edit this file 'description' to name the repository. https://git.gnuabordo.com.br/krb5-wallet.git/atom?h=debian%2F0.10-1 2010-02-22T04:31:27+00:00 Imported Upstream version 0.10 2010-02-22T04:31:27+00:00 Russ Allbery rra@stanford.edu 2010-02-22T04:31:27+00:00 urn:sha1:dfc86dd443e93c20aaaac18f270e38e631769f84 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 The wallet command-line client now reads the data for store from a 2008-04-24T23:05:14+00:00 Russ Allbery rra@stanford.edu 2008-04-24T23:05:14+00:00 urn:sha1:86bce23e53e6cc89ed5104b21a5fe33fab5a7a9f file (using -f) or from standard input (if -f wasn't given) when the data isn't specified on the command line. The data still must not contain nul characters. 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. Switch to messages-krb5 in util instead of the one built in the client 2008-04-24T01:17:48+00:00 Russ Allbery rra@stanford.edu 2008-04-24T01:17:48+00:00 urn:sha1:23b711ebacb2371915bfa4d9e0d386fa4e7cb35e library and start the transition of coding style. Correctly handle get of an empty object in the wallet client. The 2008-02-12T01:55:09+00:00 Russ Allbery rra@stanford.edu 2008-02-12T01:55:09+00:00 urn:sha1:54ccb6083d69da03c71d01a271a09554e4d63e4f empty string is valid object content. Add a full end-to-end test suite to catch protocol mismatches between the client and server, such as the one fixed in this release. Fix the wallet client to use check instead of exists. 2008-02-08T21:59:24+00:00 Russ Allbery rra@stanford.edu 2008-02-08T21:59:24+00:00 urn:sha1:da92a0d5e259a126095e120c7938c6e3be27618c Add new exists and autocreate wallet server interfaces. The first 2008-02-07T23:33:23+00:00 Russ Allbery rra@stanford.edu 2008-02-07T23:33:23+00:00 urn:sha1:f0bde61f5ecfc6a58a2c0ec0ccadbdd1332b64f8 states whether a given object exists and the second attempts to create the object using the default owner rules. Remove default owner handling from the create interface, which is now for administrators only. Remove server-side auto-creation of objects on get or store and instead have the client check for object existence and call autocreate if necessary. This removes confusion between default ACLs and administrative object creation for users who are also on the ADMIN ACL. Add a new autocreate API call that tries to create an object using the 2008-02-07T06:37:11+00:00 Russ Allbery rra@stanford.edu 2008-02-07T06:37:11+00:00 urn:sha1:45823559a1e64d6c8151a984fcd9c79bbdb57171 default ACLs. Remove autocreation support from create, which now requires that one be on the ADMIN ACL, and from get and store. The wallet client will soon know how to do the right thing. Add a check command to the wallet server to determine whether an object 2008-02-07T01:44:28+00:00 Russ Allbery rra@stanford.edu 2008-02-07T01:44:28+00:00 urn:sha1:428c88bb0a08ba2eb06c7f5181f7cbee2f7ee398 already exists.