Unnamed repository; edit this file 'description' to name the repository. https://git.gnuabordo.com.br/debian/krb5-wallet.git/atom?h=release%2F1.4 2018-06-03T22:36:42+00:00 2018-06-03T22:36:42+00:00 Russ Allbery eagle@eyrie.org 2018-06-03T22:36:21+00:00 urn:sha1:4a0b9e747c8abfca24f30b7ce1e9a725ce11474a Add SPDX-License-Identifier headers to all substantial source files. Collapse copyright years. Add some Emacs configuration for files where the copyright notice is at the end. Add a test that every file has SPDX-License-Identifier. 2018-05-28T05:05:31+00:00 Russ Allbery eagle@eyrie.org 2018-05-28T05:05:31+00:00 urn:sha1:769217510b97e23101a01d228e2b8510fd43a725 Mostly changing http eyrie.org URLs to https, but also remove my old email address in one place and switch some tests away from my old RRA_MAINTAINER_TESTS environment variable to use the Lancaster Consensus variables properly. This uncovered a bug in skipping one test unless Stanford Kerberos credentials existed. 2016-01-23T23:24:19+00:00 Russ Allbery eagle@eyrie.org 2016-01-23T23:24:19+00:00 urn:sha1:43d3a892cb5aa69234a2591bf584036970a7243e 2016-01-17T20:25:15+00:00 Russ Allbery eagle@eyrie.org 2016-01-17T20:25:15+00:00 urn:sha1:4feab8a987a345e38c44077d1042bf05ec03f0eb The versions of all of the wallet Perl modules now match the overall package version except for Wallet::Schema, which is used to version the database schema. Import the test from rra-c-util 5.10 and exclude Wallet::Schema from the tests. Go through all Perl modules and standardize the syntax for setting the version and indicating the required version of Perl. Fix a few other syntax issues while I'm in there. 2016-01-16T23:35:49+00:00 Russ Allbery eagle@eyrie.org 2016-01-16T23:34:22+00:00 urn:sha1:d2fde5b8330cab6bd6210ef99a628b1897676897 This requires changing the ACL verifier plumbing to pass object type and name all the way through when verifying ACLs. Hopefully I caught everything. 2015-12-15T06:38:46+00:00 Russ Allbery eagle@eyrie.org 2015-12-15T06:38:46+00:00 urn:sha1:3d9d10ceecdd9100e36e3eef547464edf3f341c6 When adding a new ACL, if creation of the verifier failed, we reported a pretty minimal error message claiming that the identifier was the problem. It can't possibly be the problem when the constructor fails. Report the actual failure more directly. 2015-11-19T07:47:26+00:00 Jon Robertson jonrober@stanford.edu 2015-06-09T20:06:56+00:00 urn:sha1:43f386a6e3d0c141cd732b5ef5c2be8349f51f03 When destroying an ACL nested in other ACLs, we now fail with an explanation rather than going through to remove all the places it's nested. That's more in line with how we handle trying to destroy ACLs that own things. Change-Id: I8bc0530e37c54369ec52d9b369f8fabe98def77a 2015-06-08T22:24:34+00:00 Jon Robertson jonrober@stanford.edu 2015-06-08T18:15:37+00:00 urn:sha1:86533bf43d071048d654691dc18a3004b6142081 This verifier will allow embedding one ACL in another for more flexible ACL handling. As part of thise we've also added the ability for each verifier to do a syntax check to see if a given name is valid for that verifier. For the moment this returns true for everything but Nested. Nested will check to make sure the given name is an existing group. Change-Id: Iacdf146d46ed882d57b7534058d34db6e6ec1de4 2015-06-08T22:24:34+00:00 Jon Robertson jonrober@stanford.edu 2015-06-04T17:56:30+00:00 urn:sha1:626d3ee2b94384a4ffe95d5e8a907f359ff7cbfb All error messages should now use the ACL name rather than the ADL id, for readability. Change-Id: I2d1cfe806b459ef083293df4fa0b83cb4cef673b 2015-06-08T22:24:34+00:00 Jon Robertson jonrober@stanford.edu 2015-04-17T20:30:45+00:00 urn:sha1:0f943b75d34623b6825a0acf34ee2cd965bc6799 Change-Id: I9e4632f3ff81f916f9157ef8128b20915ecded08