Originally Posted by jlv
(I am guessing Henry is working on this, but he's very evasive when I ask him about it.)
Originally Posted by Space
Yes, I've noticed that he is reluctant to talk about it, I am not sure why. I know he was looking for a 64-bit Windows beecrypt DLL, which I think, if I correctly understand what you have been saying here, should no longer be necessary to get this working in WiRNS (or LaHo, for that matter, which Henry knows NOTHING about
Originally Posted by Space
Also, jlv will be looking at making WiRNS plugins, I just wish Henry was less silent on all this, but I am sure he has his reasons...
Really, guys?! Have you not read all the posts about lawsuits and angry RTV owners and such?! You really think I want to become involved in all that?! Can you even imagine if I said something about dates and such what would happen if things didn't work out?! Plus, do you think I want to be party to any DNNA or DirecTV action because they are trying to defend themselves?! Heck, you can see that I joined this Forum back in March 2003 when I purchased by very first RTV. Why don't you search and see how many posts I made during that time after I got bawled out for asking something as simple as where to find information on how the RTVs work? I think it took me two years to get over that one! It was fortunate that I found a much calmer crowd over at PlanetReplay or I don't think that y'all would even have me around to be relying on so heavily!
Originally Posted by t.d.
Henry now has both 32-bit and 64-bit versions of BeeCrypt 4.2.1 DLLs (for Windows, obviously) -- I sent them to him today. And of course, they are not really needed, but possibly interesting none the less.
Thanks to Tom for providing me that as it saved me a lot of trouble! To be frank, I started on all this about a year ago and already had all my own test software and stuff. And, I'll let you all know that I had things working the weekend after Tom provided me with the key. However, at that time we were still "talking" with DNNA and certainly didn't want to stir the waters. Their making public the key(s) really made a difference. However, we were still "talking" to them. And, that's why WiRNS 2 still proxies to DNNA, even though I was willing to add to serve custom authcmds, which doesn't really change what it does. If I were to change WiRNS 2's vtime2 to return anything that uses the key, then that would change everything (regardless of what y'all think, so I don't want to hear it)...
In addition, if y'all look at the flurry of posts about installing WiRNS on PlanetReplay, you can well imagine that having WiRNS 3 provide vtime2 and getca4 support isn't enough! So, the three WiRNS developers are very hard at work trying to ensure that WiRNS 3 will be the best experience we can provide! Heck, we are the ones that have to support it and try to answer all the support questions! It's a lot to get accomplished in the six weeks that we were given notice!
So, rest assured that WiRNS 3 is in very good shape! I gave y'all the authcmds capability so you could continue with your experiments. If y'all want to make a vtime2 response plugin in the mean time, go for it! The login/logout are completely unnecessary, although you do have to at least respond to them. They don't do anything at all and there's no content in the response. If you have scripts returning vtime2 and getca4 responses, then it couldn't be more trivial to respond to the login and logout...
In the mean time, we really need to devote all our time to getting LaHo working as the people not using WiRNS are depending on that. Since it doesn't involve installation, at least we don't have to worry about that part. But, it has to work quite a bit different than WiRNS in having to provide custom data on demand, so that is a pretty big deal (and I'm not going to comment on it)...
So, we have plans to get a WiRNS 3 beta out just as quickly as possible. Having the BeeCrypt 64-bit DLL was a big deal to us because we really weren't crazy about the fixed constant approach, and we also want to keep things working as they were designed. Although, having to support BeeCrypt is its own can on worms, so we may have to rethink that. For us, having it work the same as DNNA is part of the enjoyment, well at least for me since I was the one who did it! But, I suppose not having to use BeeCrypt at all might be pretty convenient, I'll have to see...
So, I think that's all I'm going to say about it now. I think that if worse comes to worse, that y'all have enough tools to make things work with WiRNS2, making a vtime2 plugin probably wouldn't be all that difficult using j.m's technology as things haven't changed in that regard (and, the WiRNS that he developed it for is posted on SourceForge, so you have that to look at as well). But, barring anything out of the ordinary (and I don't want to jinx myself), I think that Robert's original post of things will be OK should hold up. Y'all really should be thanking him for all the hard work that he's done to make this all come about! He really spearheaded the whole effort even though he wasn't aware of how important the key was (since he has a 3K). But, it truely was his associations that got us a lot of the way to where we are. And, y'all really should thank Ryan, who worked very hard as he did when Zap2It closed up their development access to get us SchedulesDirect approved, for getting us the cooperation that we did! In addition, Glenn has been working the hardest on this whole thing trying to get my code ready for LaHo and trying to work out all the WiRNS installation problems! So, it has been a real team effort, and I just wanted y'all to be aware...
P.S. I didn't really proof this, so no points off for mistakes!