Hi Bob,
so to see how fahr we get, I did an strace -fp on the utsessiond
(both instances) and tried the connect again .. no reaction.
So I assume the process gets stuc in the utauthd thing ... is there
any way to get it to log some more debug than we get through syslog
after enableing all levels in auth.props ?
If I run this without encryption I get a 'NOTICE: CONNECT' after the 'NOTICE:
CLAIMED' here
nothing happens and no errors either ...
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: StartSession:In isMyTokenType
Mar 28 22:35:03 allmend utauthd: Worker7 NOTICE: CLAIMED by StartSession.m2
NAME: MicroPayflex.5004302c00130100 PARAMETERS: {terminalIPA=192.168.0.165,
type=MicroPayflex, fw=3.1_120879-05_2006.09.20.12.31, state=disconnected,
realId=5004302c00130100, cause=redirect, doamgh=false, barrierLevel=310,
realType=MicroPayflex, rawId=5004302c00130100, MTU=1500,
tokenSet=MicroPayflex.5004302c00130100, tokenSeq=1, firstServer=c0a80001,
atr.hist_len=09, namespace=IEEE802, subcause=utswitch, ddcconfig=2,
id=5004302c00130100, clientRand=sjzMa3XAG9xBNe/yVcmLGpVjMoCOw5QVtuBY5evNCxq,
realIP=c0a800a5, startRes=1920x1200:1920x1200, useReal=true,
atr=3b6900002494010301000100a9, event=insert, roamInitiated=false, pn=62884,
atr.hs=04, sn=00144f3b98ff, rawType=MicroPayflex, hw=SunRayP8-FS, initState=0,
_=1}
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: Client = [EMAIL PROTECTED]
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: Mutex.assertOwner.. locker =
Thread[Worker7,5,main], current = Thread[Worker7,5,main]
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: Terminal.requireNewAR():
calling ar.connReq
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: Mutex.assertOwner.. locker =
Thread[Worker7,5,main], current = Thread[Worker7,5,main]
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: Mutex.assertOwner.. locker =
Thread[Worker7,5,main], current = Thread[Worker7,5,main]
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: Queue: adding job : [EMAIL
PROTECTED],done = false
Mar 28 22:35:03 allmend utauthd: AdminJobQ DEBUG: Queue: returning sync job :
[EMAIL PROTECTED],done = false
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: CryptoConfigData::
tokenId=MicroPayflex.5004302c00130100
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: CryptoConfigData::enc_down_type
= none
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: CryptoConfigData::enc_up_type =
ARCFOUR
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG:
CryptoConfigData::auth_down_type = simple
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: CryptoConfigData::auth_up_type
= none
Mar 28 22:35:03 allmend utauthd: Worker7 DEBUG: CryptoConfigData::mode = soft
Mar 28 22:35:15 allmend utauthd: deviceManager0 DEBUG: DeviceManager.run():
return from getDM: devMgr =
{managerName=DeviceManager,managerId=localhost:7011,hostname=localhost,port=7011,cookie=3513978642500673192,socket=Socket[addr=/127.0.0.1,port=35954,localport=7010],min=null,[EMAIL
PROTECTED],}
Mar 28 22:35:15 allmend utauthd: deviceManager0 DEBUG: DeviceManager.run()
devMgr dump sidTbl: {}
Mar 28 22:35:15 allmend utauthd: deviceManager0 DEBUG: DevMgr done, thread
exits...
cheers
tobi
> Tobias Oetiker wrote:
> > Hi Brad,
> > Hi Bob,
> >
> > Do you know ? who does actually organize the encryption ?
> >
>
> The big picture is that utauthd passes encryption
> info to utsessiond, who passes it along to the X
> server (Xnewt on Linux) when it connects to a
> client. utauthd also tells the client what to do.
> The X server and client are responsible for
> performing the actual encryption/decryption.
>
> So you don't need a "utrestart -c", you only need
> to restart utauthd (so it picks up any crypto
> configuration change) and reconnect a Sun Ray to
> SRSS. If you do a "utrestart" with or without
> "-c" this will occur.
>
> 26D means that the client has been told by utauthd
> to expect rendering data from the X server, and it
> hasn't yet received any. The X server should start
> rendering to the client as soon as it connects.
>
> All that said, I don't know what could be going wrong
> here. Perhaps it is a library versioning issue as Brad
> and Swamiji are suspecting.
>
> Nothing in the gdm error file?
>
> -Bob
>
> > As I said, if I disable encryption all works fine.
> >
> > Using utrestart (without -c) the Xnewt that is already running does
> > not even stop ...
> >
> > About the sasl stuff, isn't this just a library dependency ?
> > lsof -p on java auth.utauthd.utauthd shows that
> >
> > java 7450 root mem REG 0,21 15660 1053494
> > /usr/lib/sasl2/libcrammd5.so.2.0.19
> >
> > is loaded ...
> >
> > In the messages file I can also see that utauthd connects ...
> >
> > Mar 28 15:16:51 allmend utauthd: Worker0 NOTICE: CLAIMED by StartSession.m2
> > NAME: MicroPayflex.5004302c00130100 PARAMETERS: {terminalIPA=192.168.0.165,
> > type=MicroPayflex, fw=3.1_120879-05_2006.09.20.12.31, state=disconnected,
> > realId=5004302c00130100, cause=redirect, doamgh=false, barrierLevel=310,
> > realType=MicroPayflex, rawId=5004302c00130100, MTU=1500,
> > tokenSet=MicroPayflex.5004302c00130100, tokenSeq=3, firstServer=c0a80001,
> > atr.hist_len=09, namespace=IEEE802, subcause=utswitch, ddcconfig=2,
> > id=5004302c00130100, clientRand=nKcN5BdRgWjJ0iuV08wGOQQdBjuUviuUc7YRLHitt2G,
> > realIP=c0a800a5, startRes=1920x1200:1920x1200, useReal=true,
> > atr=3b6900002494010301000100a9, event=insert, roamInitiated=false, pn=46459,
> > atr.hs=04, sn=00144f3b98ff, rawType=MicroPayflex, hw=SunRayP8-FS,
> > initState=0, _=1}
> >
> > an interesting effect I found, is that if I press the three keys
> > next to the cresent moon symbol on the sunray keyboard, that the
> > green markers in appear (33 D) ... but nothing else happens, when I
> > release the keys, the markers disapear again (26 D).
> >
> > cheers
> > tobi
> >
> >
> >
> > > > OK. Pull any smartcards out of a DTU. Check the
> > > > /var/opt/SUNWut/displays
> > > > files and find the display number that matches your Sun Ray MAC address.
> > > > Do a 'ps'. Do you see an Xnewt server running for that display? Do you
> > > > see any
> > > > Xnewts running? Where does gdm log its errors (sorry, I'm more familiar
> > > > with
> > > > dtlogin)?
> > > >
> > > gdm logs it's errors in /var/log/syslog only if you have Debug=true in
> > > it's config file.
> > >
> > >
> > >
> > > > Is there anything in that error log?
> > > >
> > > > You did install the SRSS gdm RPM, right? What does "rpm -q gdm" report?
> > > >
> > > He can't install the RPM as delivered as he's running a a deb based
> > > package system. Most of us running on Ubuntu have been using the GDM as
> > > delivered with some config file modifications.
> > >
> > >
> > >
> > > > -Bob
> > > >
> > > >
> > > > > cheers
> > > > > tobi
> > > > >
> > > > >
> > > > > Today Bob Doolittle wrote:
> > > > >
> > > > >
> > > > >
> > > > > > Tobias Oetiker wrote:
> > > > > >
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I have setup srss 3.1.1 on ubuntu edgy and things work about
> > > > > > > right,
> > > > > > > except for the encryption part.
> > > > > > >
> > > > > > > as soon as I run
> > > > > > >
> > > > > > > utcrypto -a enc_down_type=none enc_up_type=ARCFOUR
> > > > > > > auth_down_type=simple
> > > > > > > utrestart
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > Is utauthd still running at this point?
> > > > > >
> > > > > > Did you install the Java version in the
> > > > > > SRSS Supplemental area? What does:
> > > > > > /etc/opt/SUNWut/jre/bin/java -version
> > > > > > say?
> > > > > >
> > > > > > -Bob
> > > > > >
> > > > > >
> > > > > >
> > > > > > > I can not get a connection anymore ... the sunray remains in 26 D
> > > > > > >
> > > > > > > once I do
> > > > > > >
> > > > > > > utcrypto -d
> > > > > > > utrestart
> > > > > > >
> > > > > > > things go back to normal again ...
> > > > > > >
> > > > > > > any ideas on how to debug this ... I found not complaints in any
> > > > > > > of
> > > > > > > the logs ...
> > > > > > >
> > > > > > > cheers
> > > > > > > tobi
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > _______________________________________________
> > > > > > SunRay-Users mailing list
> > > > > > [email protected]
> > > > > > http://node1.filibeto.org/mailman/listinfo/sunray-users
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > _______________________________________________
> > > > SunRay-Users mailing list
> > > > [email protected]
> > > > http://node1.filibeto.org/mailman/listinfo/sunray-users
> > > >
> > > Brad Lackey
> > > Desktop Product Lead
> > > US Software Practice
> > > (720) 548-3339
> > > [EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> >
> >
>
> _______________________________________________
> SunRay-Users mailing list
> [email protected]
> http://node1.filibeto.org/mailman/listinfo/sunray-users
>
>
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten
http://it.oetiker.ch [EMAIL PROTECTED] ++41 62 213 9902
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
