09.05.2012 15:17, Ralph Corderoy kirjoitti:
> Mika, I think I explained adequately above. There is no warning in
> the documentation for the plugin that enabling it opens up the LAN
> to interrogation in a way that may not be obvious to the
> administrator that's having a browse of the plugins and enabling a
> few here and there.
>
There isn't warning about "Unix progstats" command giving out PID,
username, GID, configuration location, supybot binary location, config
location and Python version when Unix plugin is loaded outside
supybot-wizard.
Example output from Unix progstats:
> Process ID 30171 running as user "<censored>" and as group
"<censored>" from
> directory "/<censored>/<censored>/<censored>/<censored>" with the
> command line "/<censored>/<censored>/<censored>/supybot --daemon
/<censored>/<censored>/<censored>
> /<censored>/<censored>.conf". Running on Python <censored>
> (<censored>, <censored>, <censored>) [GCC <censored>].
I doubt that that bug, if you call it as bug, gets fixed in upstream,
because it's dead. You might have better luck moving to some fork
reporting it at their issue tracker.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
09.05.2012 15:17, Ralph Corderoy kirjoitti:
> Mika, I think I explained adequately above. There is no warning in
> the documentation for the plugin that enabling it opens up the LAN
> to interrogation in a way that may not be obvious to the
> administrator that's having a browse of the plugins and enabling a
> few here and there.
>
There isn't warning about "Unix progstats" command giving out PID,
username, GID, configuration location, supybot binary location, config
location and Python version when Unix plugin is loaded outside
supybot-wizard.
Example output from Unix progstats: /<censored> /<censored> /<censored> " with the /<censored> /<censored> /supybot --daemon /<censored> /<censored> /<censored> .conf". Running on Python <censored>
> Process ID 30171 running as user "<censored>" and as group
"<censored>" from
> directory "/<censored>
> command line "/<censored>
/<censored>
> /<censored>
> (<censored>, <censored>, <censored>) [GCC <censored>].
I doubt that that bug, if you call it as bug, gets fixed in upstream,
because it's dead. You might have better luck moving to some fork
reporting it at their issue tracker.
Supybot has currently two bugs, which can cause the bot to crash with /bugs.launchpad .net/ubuntu/ +source/ supybot/ +bug/996947 and /bugs.launchpad .net/ubuntu/ +source/ supybot/ +bug/996950 .
computer, which it's running on.
https:/
https:/
- -- /mkaysi. github. com/) || keyservers. net --recv-keys mkaysi. github. com/PGP/ key.txt) || mkaysi. github. com/PGP/ WhyDoISignEmail s.html) || mkaysi. github. com/articles/ complaining/ HTML.html) || mkaysi. github. com/articles/ complaining/ topposting. html) ||
[Mika Suomalainen](https:/
[gpg --keyserver pool.sks-
4DB53CFE82A46728](http://
[Why do I sign my
emails?](http://
[Please don't send
HTML.](http://
[Please don't
toppost](http://
[This signature](https:/ /gist.github. com/2643070) || enigmail. mozdev. org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iQIcBAEBAgAGBQJ PqmpwAAoJEE21PP 6CpGco5IgP/ iPJHWMSme2kCNF+ o22J6uSP 5duL1dXHB+ D3uFx0nbB9pTR4G 8ylbF1gDGs3o+ 88BsqgBkQZd QI5BLYR/ s4+Bp978FbpxAZM ZNh05qN8ufO9Cjf hnnCUQqo8fH 3Vgj6Rzd9xli9M2 hrQPkV1wCYG3eCG gAvDvtI9mnxL8fq 5tYp f6q8FKl5UbcHgUy 0holaEL1zqAJh3u 0GS2BA5UWHMh9eJ ZLoK g/F1s2gdNZDvvCG MpRPDr0o+ M9nU534MaEMaNrd yQcXlXXqVF 9HBz8mKloR2VSIs b7BG8oqycDcIB9E ehiSm5eprB28h0o HeHa CzvDAxdhiWd+ uoP1Wgh2+ lfxxHnNaRX2U7qD AsARRNbUh845lDw w INe8HoRtZDWDScN bh6WdvPD8gjmyeJ s7PloDiiYNFao0L peB66a+ + vXGHtlKAMWcwe1p uAKJnFLXB0ZjcGH 6JDo5K7Ts3URZbl VS6c epHdtduzaddD8Mh PA/BtzfOzt6xlMt YOrwlLHdOXEyvu8 e9K3 Khc+UN
OYa0Oct9TJD98z1
We+BA4F86BSPm9k
jiNCO2J68Ba3vgC
G/v38R0qRtMODE5
dlCHrM5YRjd9EqK
x5SU1kiTlqqb0dr
airireZupmF/
MaBX2dmJXw/
0Ko1u1A55wMk28k
QguXhqsIkOMRbIw
X8G+2pM5NDr9v+
=y9v5
-----END PGP SIGNATURE-----