Biss api service is online

ViaHussun

Donating Member
Messages
4,098
API_URI :
PHP:
api_uri : https://service.freedvb.com/biss/${API_KEY}+${TS}+${API_SIGNATURE}

Example :
PHP:
https://service.freedvb.com/biss/00000000000000004741419a05d687e0c29a2cc3360a82db00ca03ad75cd379bd4fb105a877cb4635ff815db8fe3fc3f3f86dd32d4c02617376b07218c5816d668d1b23d97520fd52359813607a3ada2c872543103376382ad7793d8778e4d04ce133177abd5e1d0053445725e461ee045a5c23b0a0aef9622306f0af3d91c1c0dd581be9de63bc4c089a592ef6d3100045a0244340cba9c0c3d04e1a56baa1260a71b9e51c56e1f70dda5c6297602cdd4051ac95993a5fbfa2bfb85f6e3b42a168ce0964cc7bfb797390719


bissapi.txt

https://mega.nz/file/ncBRmSyI#iFEVorXCXwPAubvAi3-d5HntRJKgE15-gDNrfN1b26k
 

campag5242

Feed Hunter
Messages
2,585
Thanks for the heads up. freedvb.com have previously offered crypt8 searches which weren't especially impressive in speed - is this more of the same?

I haven't tested this new service: whether it works or not, or how fast; but it appears to need only one TS payload which has the PUSI bit set (the ts header is 4741419a, so PUSI for pid 0141 & encrypted). Normally, BF would require two or three such ts packets, as only the first three bytes can be assumed/trusted to have known values 00 00 01, and as it's a 6-byte key we are looking for, we need at least 6 bytes matching the expected decrypt pattern to be hopeful we have the correct key.

Does this give any insights as to how Biss-AU may work?
 

K2TSET

Registered
Messages
125
Thanks for the heads up. freedvb.com have previously offered crypt8 searches which weren't especially impressive in speed - is this more of the same?

I haven't tested this new service: whether it works or not, or how fast; but it appears to need only one TS payload which has the PUSI bit set (the ts header is 4741419a, so PUSI for pid 0141 & encrypted). Normally, BF would require two or three such ts packets, as only the first three bytes can be assumed/trusted to have known values 00 00 01, and as it's a 6-byte key we are looking for, we need at least 6 bytes matching the expected decrypt pattern to be hopeful we have the correct key.

Does this give any insights as to how Biss-AU may work?

Let's say the the web server does have a list / DB of known BISS keys sorted in PID order and maybe a there are 10 known key for a certain PID, so it can then test the 10 keys against the 188 bytes you upload to find the 00 00 01 and give you the matching key.

But that's not AU BF for unknown key.

So you ask if it's possible to calculate the key for just 1 PUSI and I would say the will be many candidates if you only check for the 00 00 01 pattern. IF the web API actually can do that could be tested .... just take a TS and encode it with a random key upload the 188 bytes and see you you get the key..... probably not

Also if it does BF it will take some time.... like hours
 

campag5242

Feed Hunter
Messages
2,585
Your summary is likely correct: it's probably as unimpressive as their crypt8 search. I don't understand the motivation of freedvb to offer these services, they don't even seem to promote the hardware they sell.

I installed their android crypt8 app, but soon uninstalled it on seeing it respawn itself after terminating it.
 

campag5242

Feed Hunter
Messages
2,585
I suspected this was nothing more than a web crawler scraping already posted keys into a known keys list, and testing those against the single PUSI ts188 packet submitted.

During today's forum outage, this biss api online service failed to return keys for feeds which came up around the same period. Seems to fit the description above ie scraping keys already posted in public, perhaps solely from here?

That said, it's a useful addition to the toolbox.
 
Top