Bug#647262: istgt: user/password mismatch in example configuration
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
tags 647262 +upstream +confirmed
thanks
Hello Geoge,
On 01.11.2011 12:29, Geoge Shuklin wrote:
> This login/password used for communication between istgt and istgtcontrol, so I think, even in example configuration they must be same.
You are right, but I don't think that's really something which should be
fixed upstream. I do not want to introduce a Debian specific patch for
such a minor and pure esthetical problem. After all, you need to change
the password(s) anyway.
I will point upstream to your bugreport. If he wants to fix it, I'm fine
in merging the fix, otherwise I'd keep things as is.
> Ideally, those lines needed to be generated at postinst time.
No, that's not what maintainer scripts are for. There are some
possibilities to configure a daemon in postinst, but I don't think it is
feasible to do so in a comprehensive way for istgt because of a large
variety of different possibilities to run istgt. This also makes
transitions of configuration files very complicated. That's also the
reason why we do not ship a working configuration at all but refer to
the example configuration only.
- --
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJOsa/PAAoJEMcrUe6dgPNtPLQQAKvn0Lox3ssBzGNMj1vhG8Ia
GkxROnZ6G6FjXCyILEGljx7lw4JjrshbDhM6OVTZE0rIrTBQmzx4QBsJV3Oqf5wJ
UlXMqW2P7pHXZ43qy0uYIyuG424vbPgms5+XHvni6dQI8IqyzPtWVYiANMz6u4pd
jQl6KaDDW9aNGr7KmTsLEli/xzfAteDqLuGqXoczEUdzV9/YUFuHh95yOq+Dg3t4
R9Plc/HRieolpk/NSqh8TobDbFdnj9ffa6cuL4EDX+CdhHeUrtKzBa55IopuWWqh
gARtcO5N4aqybx3lTmZFhydcIAn9gldwwUxrx82GQV2z+e3phv+g3O7qNewKXtkO
7gYWtJmA3q/AqtTcl/pB1RHWrAgs7tRkAp1m/OSmPATq9QDz/ONedkB7mfLq8zX3
uhxGAVwKPyB49kQFF4hj8PBYUmRYyWHrWBufZ+TvcAf0ARrxQhdH4xRF0E8uRYU0
Vy3TmUXoyuEVyqNf6iiZkowMXWhLhvvxj79OLIa7e/+Iw6wPgaovUE1YVZaKshwM
WI5pu1tWmh21TUxYpb3LZmPqmM29pYXTTuHox0vsJePW3iqn0rWO+Y5ct+LqdTzP
KMhaXCJ7OUiQjl73HKIPvtnSpAdd22r3/5049Ihhu0FN+4Dele5nqtcv/rWbW10E
kvXSi+PVZIKPSwuS81K1
=0nOA
-----END PGP SIGNATURE-----
Reply to: