SageTV and crl.microsoft.com Why?

[griffpa]

I just installed a port monitoring program and noticed SageTV is trying to connect to crl.microsoft.com using ports (local=2164; remote=80). Another SageTV process is constantly listening to local port 2164. What's going on here? Thanks.

[fidget]

Originally posted by griffpa
I just installed a port monitoring program and noticed SageTV is trying to connect to crl.microsoft.com using ports (local=2164; remote=80). Another SageTV process is constantly listening to local port 2164. What's going on here? Thanks.

I don't know about crl.microsoft.com, but I would guess that port 2164 is the SageTV server address (so you can connect clients to SageTV).

[carlgar]

SageTV should only use these ports:
port 42024 is for the client/server connection
port 7818 is for streaming
port 7760 is for the EPG download

[Alex0230]

I did some research on this, there is a sister site: crl.verisign.com

It appears that this has something to do with how windows handles digital certificates and secure connections.... 'certificate revocation list'

Here's a thread that talks about it:
http://64.233.167.104/search?q=cache...5&ie=UTF-8</a>

[griffpa]

I killed the process which made Sage shut-down. When I launched Sage again, the process did not restart. Maybe it's something that happens during initial boot or when Sage downloads the latest listings. Maybe it has something to do with Java or a component of SageTV.

In any case, I would like to hear from the developers to make sure (1) there isn't a security risk and (2) this process which appears to be hung, is not eating up memory or performance. I ran a utility that optimizes Win XP, and it always reports Sage as using an unusually high amount of memory. Maybe it's a related problem.

[fidget]

I just had a thought. Are you running the Microsoft JVM? crl looks an awful lot like "Common Runtime Library" or some such. A google search returned this interesting link.