-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Russell Blau:

How does one know what their LDAP password is?

You can set it by running "setpass".

- river.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Russell Blau:

Nightshade accepted my current password in 'setlicense', but willow did not.

This should be fixed now.

- river.

Mike.lifeguard:

How would someone check the default license a user set if they needed to?

River Tarnell:

willow% ldapsearch -h ldap -b ou=people,o=unix,o=toolserver '(uid=rriver)'

tsDefaultLicense

version: 1 dn: uid=rriver,ou=People,o=unix,o=toolserver tsDefaultLicense: zlib

Could this be made into a command to make it easier, such as the following:

#!/bin/bash echo `ldapsearch -h ldap -b ou=people,o=unix,o=toolserver '(uid=$1)' tsDefaultLicense` | grep tsDefaultLicense

Just a thought

stwalkerster

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Conrad Irwin:

SASL/EXTERNAL authentication started ldap_sasl_interactive_bind_s: Unknown authentication method (-6)

I get this for all invocations of ldapsearch - do I need to do something else to enable it?

On which server?

- river.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Conrad Irwin:

On 24 May 2010 19:14, River Tarnell river.tarnell@wikimedia.de wrote:

...

Conrad Irwin:

...

SASL/EXTERNAL authentication started ldap_sasl_interactive_bind_s: Unknown authentication method (-6)

...

On which server?

nightshade.

Try adding the -x option.

- river.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Mike.lifeguard:

How would someone check the default license a user set if they needed to?

The following one-liner might also be interesting:

ldapsearch -h ldap -b o=unix,o=toolserver \ '(&(objectclass=posixAccount)(tsDefaultLicense=*))' tsDefaultLicense \ | sed -n '/^dn:/ { N; s/^dn: uid=([^,]*).*tsDefaultLicense: (.*)/\1:\2/; p; }' | nawk -F: '{ printf("%-16s %s\n", $1, $2); }'

- river.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Max Semenik:

How can I set a default license for a multi-maintainer project? Currently, setlicense requires setpass which returns "you don't seem to be logged in".

Currently MMTs can't have LDAP passwords, which means you can't set a license. I'm not sure a default license for an MMT is very useful, since generally an MMT will only have a single project, and it will have a license. Projects without licenses tend to be small tools hacked together quickly by a single user, who doesn't think to add a license header.

- river.

On 05/24/2010 09:07 PM, Nikola Smolenski wrote:

Дана Monday 24 May 2010 17:04:17 River Tarnell написа:

...

We have now introduced the concept of a default license for each account. This is documented on the wiki: https://wiki.toolserver.org/view/Default_license.

"Every account has a default license. This is the license that your tools [...]"

Do we have the definition of a a tool? Only scripts that are publically accessible, or any code that runs on the Toolserver?

My http://toolserver.org/~vyznev/LICENSE file, which I wrote back when this was last discussed in February, starts with:

"Unless stated otherwise, all source code written by me and stored under my Toolserver account, whether normally accessible to the public or not, shall be considered to have been released under the following license and disclaimer."

While I originally chose this broad definition just for my own use, I think it's actually a fairly sensible one. Obviously, I can't release any code that I'm not the author of -- and on the other hand, if I have any code stored on my Toolserver account that I don't wish to license, all I need to do is add a comment saying "All rights reserved" to it.

(Ps. I just realized that I'd never actually sent the long message I wrote in February regarding default licensing to the list. Oh well. The now introduced implementation is not exactly like the one I was advocating in that message, but it'll hopefully serve just as well.)

Mashiah Davidson schrieb:

...

We have now introduced the concept of a default license for each account.  This is documented on the wiki: https://wiki.toolserver.org/view/Default_license.

It doesn't look working for me. Asks for LDAP password, then asks if I want to change the license and on any answer exits with no questions on which license I want to set as a default.

This behaviour is common for nightshade and willow.

Did you try to answer with 'yes'? Every other combination of characters seems to abort.