what the fuck?<br><br><div class="gmail_quote">2013/6/2 קראק אר <span dir="ltr"><<a href="mailto:cracker787@gmail.com" target="_blank">cracker787@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="rtl"><div dir="ltr">FUCK YOU ALL, Don't send me messages ever again!</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div dir="ltr">2013/5/31 Jens Langner <span dir="ltr"><<a href="mailto:J.Langner@hzdr.de" target="_blank">J.Langner@hzdr.de</a>></span></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">Hello Aaron,<br>
<br>
Am 31.05.2013 um 13:07 schrieb Aaron Sowry <<a href="mailto:aaron@cendio.se" target="_blank">aaron@cendio.se</a>>:<br>
<div><br>
>> 1) As we supply the password on command-line via the "-p" option<br>
>> potential hackers could easily retrieve the user password in clear text<br>
>> by simply listing all running processes via the "ps" command on linux.<br>
><br>
> There are actually 2 ways to achieve this with ThinLinc:<br>
><br>
> 1) The ThinLinc client has an option "--askpass PROGRAM" (see "tlclient<br>
> --help" and [1]). Whether this will work for you or not depends on the<br>
> program which is asking the user for their login information, however it<br>
> is worth a look.<br>
<br>
</div>Thanks for the hint in using the --askpass / -P option. In fact, I think I found a way to read in the password from stdin and supply it via -P to thinlinc. Our current solution seems to be executing the thinlinc client via the following command-line sequence:<br>
<br>
echo PASSWORD | /opt/thinclient/bin/tlclient -u USERNAME -P cat SERVERNAME<br>
<br>
Thus, by using "cat" as the askpass command the password is supplied via a stdin pipe to tlclient will immediately be forwarded to the thinlinc client (stdin redirection). This seems to work now, however, it is IMHO rather uncommon to do it that way.<br>
<div><br>
> 2) Specify a per-user client configuration file, which contains the<br>
> password. This configuration file will have the same format as<br>
> ~/tlclient.conf, and should be set with the appropriate permissions. You<br>
> will need to set the PASSWORD parameter (see [2]) using hexadecimal<br>
> ASCII representations of the password characters. For example, for a<br>
> password of "foo":<br>
><br>
> PASSWORD=666F6F<br>
><br>
> In your case, you will probably also want to set AUTOLOGIN=1 as well as<br>
> SERVER_NAME. The ThinLinc client can then be launched as follows:<br>
><br>
> $ tlclient -C <conf_file><br>
<br>
</div>We also thought about using an automatically generated config file in first place and supply it to the client, but we didn't want to generate such a file and risk seeing it being intercepted in some way. If we don't find any other problem I think our request is indeed be fulfilled with the "-P cat" solution.<br>
<div><br>
>> 2) When automatically connecting to a thinlinc server by calling the<br>
>> client with username, password and server name the client GUI always<br>
>> pops up while trying to connect to the ThinLinc server. There is,<br>
>> however, no option to suppress the ThinLinc client user interface<br>
>> completely.<br>
><br>
> We do in fact have a feature-request bug for this already in our tracker<br>
> (bug #2897). It has not been implemented yet, however. If this feature<br>
> is important to you, and you would like to make a feature request for<br>
> it, you can send a mail to <a href="mailto:support@cendio.se" target="_blank">support@cendio.se</a> and we can discuss this<br>
> further off-list.<br>
<br>
</div>Thanks for pointing me to that feature request. Indeed, this feature is really somewhat important to us as popping up the thinlinc client somehow distracts the user attention. I will therefore bring up my request to <a href="mailto:support@cendio.se" target="_blank">support@cendio.se</a> soon in the hope to such such a quiet option being implemented in a future client version.<br>
<div><div><br>
best regards,<br>
jens<br>
--<br>
Dr. Jens Langner<br>
Helmholtz-Zentrum Dresden-Rossendorf<br>
Institute of Radiopharmaceutical Cancer Research<br>
Department of Positron Emission Tomography<br>
POB 51 01 19, 01314 Dresden, Germany<br>
<a href="http://www.hzdr.de/" target="_blank">http://www.hzdr.de/</a> | +49 351 260 2757<br>
<br>
Vorstand: Prof. Dr. Dr. h. c. Roland Sauerbrey<br>
Prof. Dr. Dr. h. c. Peter Joehnk<br>
VR 1693 beim Amtsgericht Dresden<br>
<br>
</div></div><br></div></div>_______________________________________________<br>
Thinlinc-technical mailing list<br>
<a href="mailto:Thinlinc-technical@lists.cendio.se" target="_blank">Thinlinc-technical@lists.cendio.se</a><br>
<a href="http://lists.cendio.se/mailman/listinfo/thinlinc-technical" target="_blank">http://lists.cendio.se/mailman/listinfo/thinlinc-technical</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Thinlinc-technical mailing list<br>
<a href="mailto:Thinlinc-technical@lists.cendio.se">Thinlinc-technical@lists.cendio.se</a><br>
<a href="http://lists.cendio.se/mailman/listinfo/thinlinc-technical" target="_blank">http://lists.cendio.se/mailman/listinfo/thinlinc-technical</a><br>
<br></blockquote></div><br>