<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>Hi,</div>
<div> </div>
<div>I found an old thread here:</div>
<div> </div>
<div><a href="http://lists.cendio.se/pipermail/thinlinc-technical/2016-February/005779.html"><font color="#0563C1"><u>http://lists.cendio.se/pipermail/thinlinc-technical/2016-February/005779.html</u></font></a></div>
<div> </div>
<div>Where someone asked about getting Thinlinc to auto-unlock a gnome-keyring.</div>
<div> </div>
<div>I was wondering if anyone else has made any progress on this in the last couple of years?</div>
<div> </div>
<div>I think the one issue that the poster of that thread may have had left is this part of the documentation of “gnome-keyring-daemon --login”:</div>
<div> </div>
<div>“It reads all of stdin (including any newlines) as a login password”</div>
<div> </div>
<div>It seems tl-sso-password adds a newline at the end of its output, and hence “gnome-keyring-daemon --login” will probably always fail because it takes that newline as part of the password.</div>
<div> </div>
<div>So I have created the following script, which I have put in /opt/thinlinc/libexec/tl-gnome-keyring.sh, and created a symbolic link to from /opt/thinlinc/etc/xstartup.d/05-tl-gnome-keyring.sh (as that seems to be how the other startup scripts work)</div>
<div> </div>
<div>#!/bin/bash</div>
<div># -*- mode: shell-script; coding: utf-8 -*-</div>
<div>#</div>
<div># MF: Attempt to unlock gnome keyring</div>
<div>#</div>
<div># actuib: Unlock gnome keyring with SSO passwrd</div>
<div>if type gnome-keyring-daemon > /dev/null 2>&1; then</div>
<div> if "${TLPREFIX}/bin/tl-sso-password" --check; then</div>
<div> "${TLPREFIX}/bin/tl-sso-password" | tr -d '\n\r' | gnome-keyring-daemon --login</div>
<div> fi</div>
<div>fi</div>
<div> </div>
<div>It seems to be working for me (and not if I use an SSH key instead of a password to login - doh!). Obviously the “tr” command will remove any newlines or carriage returns, not just those at the end. A better fix would be a CLI option to “tl-sso-password”
not to add a newline, but it is extremely unlikely that most users will have a newline or carriage return embedded in their password.</div>
<div> </div>
<div>Is there anything anyone can see wrong in what I have added that would cause problems later?</div>
<div> </div>
<div>Should there be a call to “tl-sso-password --remove” somewhere at the end of the startup process? I am a little concerned that there is a command available within the session that will dump my password to standard output in plain text!</div>
<div> </div>
<div>Thanks</div>
<div> </div>
<div>Michael</div>
<div> </div>
</span></font>
</body>
</html>