RunUO Community
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Latest Razor Source and Releases
- Thread starter buggles
- Start date
Too bad Mark did not released the Crypt.dll/linker sources, even that I can bypass the crypt.dll and run my own Razor build, it would be nice to see how they accomplished the packet sniffing and other client control functionalities
I believe that Mark did not released to avoid people using Razor to bad things, like bypass the server blocked features
I believe that Mark did not released to avoid people using Razor to bad things, like bypass the server blocked features
Someone asked him why on reddit and he answered: http://www.reddit.com/r/ultimaonline/comments/1yicqj/razor_github_repository/
Grimoric
Sorceror
Well my 2 cents on this, UO Crypto is already out there it is not something new even UOX used it back in time and have full source for it.
Do it on the fly decrypt calculate also exists and packet injection.
http://yoko.com.ua/eng/injection.htm
Full opensource clone of UOAssists based on Yoko injection dlls.
http://injection.sourceforge.net/
Packet hooker for UO in .NET.
http://www.runuo.com/community/threads/spyuo-a-c-uo-packet-hooker.15411/
Razor have only released the .net crap that was already out. It was easy to reverse with Telriks tool JustDecompile.
http://www.telerik.com/products/decompiler.aspx
There is alot of information on how this works if you just know what to look for and where to look for it, this is just some small hints on where to start.
I guess that it have to be another reason they dont want us to read their source. (bad written code or probably stolen code? Yoko project?)
Do it on the fly decrypt calculate also exists and packet injection.
http://yoko.com.ua/eng/injection.htm
Full opensource clone of UOAssists based on Yoko injection dlls.
http://injection.sourceforge.net/
Packet hooker for UO in .NET.
http://www.runuo.com/community/threads/spyuo-a-c-uo-packet-hooker.15411/
Razor have only released the .net crap that was already out. It was easy to reverse with Telriks tool JustDecompile.
http://www.telerik.com/products/decompiler.aspx
There is alot of information on how this works if you just know what to look for and where to look for it, this is just some small hints on where to start.
I guess that it have to be another reason they dont want us to read their source. (bad written code or probably stolen code? Yoko project?)
Zippy
Razor Creator
Actually I think the code is pretty good 
Definitely not stolen.
I think Mark answered pretty well why. The Crypt.dll does a little "authorization" with Razor before it will let any data through. Allowing people to take Razor and make their own seems like sort of a bad idea. And I think it is very significantly easier to take the Razor C# and make a few mods than to start with Injection and make something that is usable. I'm probably being paranoid, though, I admit that. If Injection was sufficient for someone to build their own Assistant tool, wouldn't there be more of them in existence now?
There is another reason, and that's there were a couple of different "Cheat detection" methods used by the real UO servers and by UOGamers which have code to deal with them in Crypt.dll. I don't know if any of those methods are still in use, but removing them from Crypt.dll is non-trivial, and we wouldn't want to expose those methods if they're still in use today.
Definitely not stolen.
I think Mark answered pretty well why. The Crypt.dll does a little "authorization" with Razor before it will let any data through. Allowing people to take Razor and make their own seems like sort of a bad idea. And I think it is very significantly easier to take the Razor C# and make a few mods than to start with Injection and make something that is usable. I'm probably being paranoid, though, I admit that. If Injection was sufficient for someone to build their own Assistant tool, wouldn't there be more of them in existence now?
There is another reason, and that's there were a couple of different "Cheat detection" methods used by the real UO servers and by UOGamers which have code to deal with them in Crypt.dll. I don't know if any of those methods are still in use, but removing them from Crypt.dll is non-trivial, and we wouldn't want to expose those methods if they're still in use today.