<feed xmlns='http://www.w3.org/2005/Atom'>
<title>krb5-wallet.git/server/wallet-backend, branch debian/1.0-3</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.gnuabordo.com.br/krb5-wallet.git/atom?h=debian%2F1.0-3</id>
<link rel='self' href='https://git.gnuabordo.com.br/krb5-wallet.git/atom?h=debian%2F1.0-3'/>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/'/>
<updated>2013-03-28T02:02:00+00:00</updated>
<entry>
<title>Accept any characters in the argument to the comment command</title>
<updated>2013-03-28T02:02:00+00:00</updated>
<author>
<name>Russ Allbery</name>
<email>rra@stanford.edu</email>
</author>
<published>2013-03-28T01:23:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=945608173ffc08cd1351433100dcc869aa6dafb1'/>
<id>urn:sha1:945608173ffc08cd1351433100dcc869aa6dafb1</id>
<content type='text'>
It's nice to have spaces and other special characters in comments,
so allow any character rather than applying the normal argument
filtering.

Change-Id: Iec8584f1f6893906db7245fbe571d62ebc60f72a
Reviewed-on: https://gerrit.stanford.edu/989
Reviewed-by: Russ Allbery &lt;rra@stanford.edu&gt;
Tested-by: Russ Allbery &lt;rra@stanford.edu&gt;
</content>
</entry>
<entry>
<title>Allow owners of objects to destroy them by default</title>
<updated>2013-03-27T19:52:58+00:00</updated>
<author>
<name>Russ Allbery</name>
<email>rra@stanford.edu</email>
</author>
<published>2013-03-27T19:51:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=f6c63bdb2be5ccc0c6133bf87025d37805579005'/>
<id>urn:sha1:f6c63bdb2be5ccc0c6133bf87025d37805579005</id>
<content type='text'>
Owners of wallet objects are now allowed to destroy them.  In previous
versions, a special destroy ACL had to be set and the owner ACL wasn't
used for destroy actions, but operational experience at Stanford has
shown that letting owners destroy their own objects is a better model.

Change-Id: I0e97d7a000e62cf5321add7b44140db6edc6769f
Reviewed-on: https://gerrit.stanford.edu/973
Reviewed-by: Russ Allbery &lt;rra@stanford.edu&gt;
Tested-by: Russ Allbery &lt;rra@stanford.edu&gt;
</content>
</entry>
<entry>
<title>Add explicit license statements to all POD documentation</title>
<updated>2013-02-28T00:54:08+00:00</updated>
<author>
<name>Russ Allbery</name>
<email>rra@stanford.edu</email>
</author>
<published>2013-02-27T23:49:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=1a4ec451eb04fabe9039fd9a13f63865f6b32e01'/>
<id>urn:sha1:1a4ec451eb04fabe9039fd9a13f63865f6b32e01</id>
<content type='text'>
For scripts, do this by moving the copyright and license statement
from the top of the script into the POD documentation.

Also try to uniformly put the SEE ALSO section last.

Change-Id: Id31a5c0d5e6f6831a689deec41a13d35bb40465a
Reviewed-on: https://gerrit.stanford.edu/850
Reviewed-by: Russ Allbery &lt;rra@stanford.edu&gt;
Tested-by: Russ Allbery &lt;rra@stanford.edu&gt;
</content>
</entry>
<entry>
<title>Add new acl check command</title>
<updated>2012-11-04T18:38:29+00:00</updated>
<author>
<name>Russ Allbery</name>
<email>rra@stanford.edu</email>
</author>
<published>2012-11-04T18:38:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=357532f312aea30ab5b3e459ccf19f1580b29262'/>
<id>urn:sha1:357532f312aea30ab5b3e459ccf19f1580b29262</id>
<content type='text'>
Add a new acl check command which, given an ACL ID, prints yes if that
ACL already exists and no otherwise.  This is parallel to the check
command for objects.

Also fix some documentation errors in the wallet client documentation,
saying that the check command doesn't require any ACL and fixing one
place where "show" was used instead of "store".
</content>
</entry>
<entry>
<title>Add a comment field to objects</title>
<updated>2011-06-20T23:15:35+00:00</updated>
<author>
<name>Russ Allbery</name>
<email>rra@stanford.edu</email>
</author>
<published>2011-06-20T23:15:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=74ed6945f9c7839603764327f0187897525db453'/>
<id>urn:sha1:74ed6945f9c7839603764327f0187897525db453</id>
<content type='text'>
Add a comment field to objects and corresponding commands to
wallet-backend and wallet to set and retrieve it.  The comment field
can only be set by the owner or wallet administrators but can be seen
by anyone on the show ACL.
</content>
</entry>
<entry>
<title>Add a krb5-regex ACL type</title>
<updated>2010-06-29T22:30:51+00:00</updated>
<author>
<name>Ian Durkacz</name>
<email>idurkacz@inf.ed.ac.uk</email>
</author>
<published>2010-06-29T22:30:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=b573d6f433725afda0e4238f63a5b3485d1d56f4'/>
<id>urn:sha1:b573d6f433725afda0e4238f63a5b3485d1d56f4</id>
<content type='text'>
Add the krb5-regex ACL type and corresponding Wallet::ACL::Krb5::Regex
module.  This ACL is identical to krb5 except that it takes a regular
expression matching principals instead of a string that must match
exactly.
</content>
</entry>
<entry>
<title>Update documentation for support for storing nul data</title>
<updated>2010-02-21T05:52:38+00:00</updated>
<author>
<name>Russ Allbery</name>
<email>rra@stanford.edu</email>
</author>
<published>2010-02-21T05:52:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=3b3e387b6bca35a00a86ad41e39874eeadcb78b9'/>
<id>urn:sha1:3b3e387b6bca35a00a86ad41e39874eeadcb78b9</id>
<content type='text'>
Update the wallet client, wallet-backend, and Wallet::Object::File
documentation for the support for storing data containing nul
characters using the new stdin support in remctld.  Add this to NEWS.
</content>
</entry>
<entry>
<title>wallet-backend gets the third store argument from stdin if missing</title>
<updated>2010-02-21T04:30:37+00:00</updated>
<author>
<name>Russ Allbery</name>
<email>rra@stanford.edu</email>
</author>
<published>2010-02-21T04:30:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=4f863ccc9531130be3f4aecea341a0e8a66c6f8c'/>
<id>urn:sha1:4f863ccc9531130be3f4aecea341a0e8a66c6f8c</id>
<content type='text'>
If there is no third argument to store, read it from standard input
instead.  This is the preferred way of running wallet-backend, using
stdin=last support from remctl 2.14 and later.  Receiving the third
argument as a regular argument continues to be supported for backward
compatibility.
</content>
</entry>
<entry>
<title>Reorganize main POD tests and add a spelling check</title>
<updated>2010-02-10T07:57:10+00:00</updated>
<author>
<name>Russ Allbery</name>
<email>rra@stanford.edu</email>
</author>
<published>2010-02-10T07:57:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=5d7f614e88bac459a693f1dcc91aad36ed3d00dd'/>
<id>urn:sha1:5d7f614e88bac459a693f1dcc91aad36ed3d00dd</id>
<content type='text'>
Add a POD spelling test to the non-Perl-module part of the code and
move the documentation tests into a separate directory.  Merge the
POD syntax tests between client and server into one test.

Reformat all of the POD documentation to use 74 columns.  Fix a few
revealed spelling errors or weird wordings.
</content>
</entry>
<entry>
<title>Remove the sync documentation from wallet-backend</title>
<updated>2010-02-09T21:42:01+00:00</updated>
<author>
<name>Russ Allbery</name>
<email>rra@stanford.edu</email>
</author>
<published>2010-02-09T21:42:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/krb5-wallet.git/commit/?id=1ec1398452733d861b1b68253e6de0b8cb9f757f'/>
<id>urn:sha1:1ec1398452733d861b1b68253e6de0b8cb9f757f</id>
<content type='text'>
The code to support the attribute is still present in case we add a
system with which to synchronize later on.
</content>
</entry>
</feed>
