[DiscordArchive] Hey, I'm trying to make caschost working for 11.0.2 (for custom roleplay server) and I met the KeyRi
[DiscordArchive] Hey, I'm trying to make caschost working for 11.0.2 (for custom roleplay server) and I met the KeyRi
Original source
Hey, I'm trying to make caschost working for 11.0.2 (for custom roleplay server) and I met the KeyRing file, which was actually missing. Is there any info about it?
For context:
I'm running the caschost locally and for running client I use arctium launcher, changing cdns and versions urls.
Then I receive an error:
`Tact instance creation failed. Error(1): unknown failure.`
But in caschost terminal I see the logs:
`Request reached the end of the middleware pipeline without being handled by application code. Request path: GET http://localhost:5100/tpr/wow/config/3c/...4d2a03a0cd, Response status code: 404`
And this "3ca57fe7319a297346440e4d2a03a0cd" is exactly what I see in versions file under KeyRing field. I tried to find any information about this, but I'm not sure I got it right.
Basically, I was able to get the file via wireshark when ran the wow itself and just manually put it into Output/ folder (I know it's not how caschost supposed to be worked with, just for testing reasons). As expected, the error from host logs vanished, but wow client still has the same error (I believe, my root is not written right, wip).
So, for now the question - what is this keyring file? Can I ignore it for now?
rektbyfaith
09-30-2024, 03:37 AM #1Archived author: Глупая • Posted: 2024-09-30T03:37:59.511000+00:00
Original source
Hey, I'm trying to make caschost working for 11.0.2 (for custom roleplay server) and I met the KeyRing file, which was actually missing. Is there any info about it?
For context:
I'm running the caschost locally and for running client I use arctium launcher, changing cdns and versions urls.
Then I receive an error:
`Tact instance creation failed. Error(1): unknown failure.`
But in caschost terminal I see the logs:
`Request reached the end of the middleware pipeline without being handled by application code. Request path: GET http://localhost:5100/tpr/wow/config/3c/...4d2a03a0cd, Response status code: 404`
And this "3ca57fe7319a297346440e4d2a03a0cd" is exactly what I see in versions file under KeyRing field. I tried to find any information about this, but I'm not sure I got it right.
Basically, I was able to get the file via wireshark when ran the wow itself and just manually put it into Output/ folder (I know it's not how caschost supposed to be worked with, just for testing reasons). As expected, the error from host logs vanished, but wow client still has the same error (I believe, my root is not written right, wip).
So, for now the question - what is this keyring file? Can I ignore it for now?
Original source
Omg wtf
rektbyfaith
09-30-2024, 03:49 AM #2Archived author: Azarchius • Posted: 2024-09-30T03:49:14.764000+00:00
Original source
Omg wtf
Original source
Thank you I'll check it asap
rektbyfaith
09-30-2024, 03:49 AM #3Archived author: Azarchius • Posted: 2024-09-30T03:49:20.518000+00:00
Original source
Thank you I'll check it asap
Original source
You're not going to get caschost working with any 11.x or late 10.x client due to missing TVFS support.
But yes, you can pretty much ignore keyring, it's just another tact key delivering mechanism so the client can decrypt intro cinematics (as keys are usually delivered later when connecting to the world server, keyring makes sure they are known immediately).
rektbyfaith
09-30-2024, 05:00 AM #4Archived author: Marlamin • Posted: 2024-09-30T05:00:48.101000+00:00
Original source
You're not going to get caschost working with any 11.x or late 10.x client due to missing TVFS support.
But yes, you can pretty much ignore keyring, it's just another tact key delivering mechanism so the client can decrypt intro cinematics (as keys are usually delivered later when connecting to the world server, keyring makes sure they are known immediately).
Original source
Well, I see cascexplorer reads 11.x without going through tvfs root-sources. So I thought it may be possible more-less.
rektbyfaith
09-30-2024, 05:04 AM #5Archived author: Глупая • Posted: 2024-09-30T05:04:44.479000+00:00
Original source
Well, I see cascexplorer reads 11.x without going through tvfs root-sources. So I thought it may be possible more-less.
Original source
CASCExplorer still reads the old root file as Blizzard still updates and uses it, but the WoW client also requires and uses the newer TVFS manifests too
rektbyfaith
09-30-2024, 05:05 AM #6Archived author: Marlamin • Posted: 2024-09-30T05:05:28.977000+00:00
Original source
CASCExplorer still reads the old root file as Blizzard still updates and uses it, but the WoW client also requires and uses the newer TVFS manifests too
Original source
So that requires patching too now
rektbyfaith
09-30-2024, 05:05 AM #7Archived author: Marlamin • Posted: 2024-09-30T05:05:57.067000+00:00
Original source
So that requires patching too now
Original source
Ok... That makes sense.
WowTVFSRootHandler from CASClib is not working then?
rektbyfaith
09-30-2024, 05:09 AM #8Archived author: Глупая • Posted: 2024-09-30T05:09:44.405000+00:00
Original source
Ok... That makes sense.
WowTVFSRootHandler from CASClib is not working then?
Original source
It works fine when enabled, reading TVFS isn't the problem, it is writing it
rektbyfaith
09-30-2024, 05:10 AM #9Archived author: Marlamin • Posted: 2024-09-30T05:10:17.456000+00:00
Original source
It works fine when enabled, reading TVFS isn't the problem, it is writing it
Original source
But TVFS is missing some data still and is slower to parse in CASCLib so old root is still default
rektbyfaith
09-30-2024, 05:10 AM #10Archived author: Marlamin • Posted: 2024-09-30T05:10:57.369000+00:00
Original source
But TVFS is missing some data still and is slower to parse in CASCLib so old root is still default
1 Guest(s)
1 Guest(s)