#[Dev] Self-hosting JITStreamer?

1 messages · Page 1 of 1 (latest)

sharp badge
#

I'd like to be able to use JIT on the go, so I thought I'd give JitStreamer a try. I don't like using 3rd party servers (for security), so I managed to compile it and netmuxd, and start up my own server with WireGuard. I haven't yet tried using it, but I was curious if someone could answer a few questions I wanted to know first.

First off, I am curious if there's any chance of my device/account being locked for using JitStreamer. I know this might sound silly, but I can't risk it, and I saw that JitStreamer needs you to "pair" your device. Is this the same sort of pairing that you have to have a device paired for AltServer with Anisette or a Windows PC, or is it something different.?

Secondly, are there any other risks associated to pairing a Jit server to my device (if that's what it's doing). I assumed it was just attaching a remote debugger, but needing to "pair" and require a code makes it seem like there's more to it. I don't want to take any big account risks or anything seeing that I may be sharing this server with a couple friends and don't want to be "that person"

Also no, I don't want to use SideStore Jit. I have reasons.

drifting ridge
#

JitStreamer doesnt work anymore

sharp badge
drifting ridge
sharp badge
#

That doesn’t say anything about it being broken

#

The official one is just gone

#

That’s fine if y’all are focusing on something new/better, but I like this solution more and intend to run my own as long as it works. I don’t need any technical support or anything, and can fully understand if y’all don’t want to support it in favour if the new solution, but if anyone with the knowledge could take a few moments to help me with a little bit of information, that would be great

lean mango
# sharp badge I'd like to be able to use JIT on the go, so I thought I'd give JitStreamer a tr...

Hello! Basically the pairing is the same pairing file that SideStore uses, just in a different way. Basically, you generate a pairing file between an iOS device and a computer when you go through the “Trust Computer” dialog. When you trust a computer, you share a pairing file from the iOS device to the computer that allows the computer to wirelessly access your iOS device, including developer access. Tools like jitterbugpair and JitStreamer’s method intercept this pairing file, and write it to disk, allowing JitStreamer/SideStore to connect to your device wirelessly. There is no chance of your account being locked as there is no association between pairing files and Apple IDs, only devices. The risk you run with JitStreamer is that your pairing file is hosted on a server that can be compromised, and if someone gains access to your VPN network while your iOS device has it enabled and they have your pairing file, they can do all sorts of nasty things to your device like download any app, or deleting/reading apps on your device/etc. SideStore doesn’t have that issue since it’s all on device, but if you personally host your own JitStreamer you should be relatively safe. If you have any other questions, be sure to ping me!

#

We also did fix the SideStore locking accounts issue. The reason things like AltStore/SideStore need a code from your Apple ID is because we log into the Xcode APIs directly from the app. Typically that can only be done from a Mac, but with the anisette server solution we can generate a fake Mac for you to then allow access to the Xcode APIs. AltStore doesn’t have this issue because they typically use AltServer for their anisette, whereas SideStore wanted to get rid of the dependency on AltServer. Anisette’s still a thing we would love to get fully on device, but we’re still a bit from that.

sharp badge
#

Thanks for the help!

#

That's just what I wanted to know

dense sandal
#

How do you set up Jitstreamer?

#

Jitstreamer?

lean mango
#

[Leg] Self-hosting JITStreamer?