Well Apple did some changes this week in the Siri protocol let analyse them

1. Apple sends a set activation token that is ignored by most devices using Spire, including the 4s
This doesn't affect much devices except that sometimes when they connect to other servers they need to delete the assistant.plist. Why? I gues because it wasn't activated before or something like that. Need more time to analyze the packets and find out why! (I was currently focused on the Validation expiration system)

2.The validation expiration

Some time before when a device used invalid or expired 4s data and made a request to guzzoni servers, Guzzoni replied with Validation Expired or command Failed.
This made it easy for proxies to detect these relies and set the invalid 4s key as expired!
Apple changed the above method, in my opinion due to similar to DDOS attacks behavior when the Validation data where invalid!
Now Guzzoni wont reply back to packets that have invalid or expired validation thus making it hard to detect invalid keys.

I made a work around this and i can find witch keys have expired with the help of packet analysis!
Lets see how this works:

1. A device makes a request with a valid key.

Apple sends the activation token
The proxy server detects the token and increases the total activation tokens for this key by one

2. A device makes a request with an invalid key

Apple wont send the activation token
The proxy server detects a finishspeech (waiting for recognition) request without an activation token, and increases the finishspeech requests for this key by one

3. When the Finishspeech requests are more than the sensitivity nubmer (5) and NO activation token is recieved then the key is marked as expired!

In short, if a key is used and apple wont reply back after some tries (sensitivity) then the key is marked as expired.

Its a complicated algo and this is a very short description of how this works!

Cheers,

Jimmy

The Three Little Pigs Siri Proxy
This Server is based on @kmsbueromoebel proxy combined with Plamoni's Siri Proxy

Give them also gredits for this project

OS: Linux Prefered and tested
Language: Ruby/PHP
Database support: My SQL
Demo-site: down for now!

Version 0.8b

*Updated with new Web-Interface! Thanks to @WouterDS
**Updated with plugins thanks to @thpryrchn

Features

Plugins api and config capable (NEW). Now Enjoy Your new plugins!
E-Mail Notifications! (New)
MySql Database connection support: Supports MySQL database connection for storing configuration,keys and runtime statistics.
Multiple key support: You can connect more than 1 iPhone4S and store even more keys. The more the keys, the more the clients!
Key Throttling: Each client uses a different key, if more than one Keys are available. The throttler makes sure that each Key is throttled thus enabling several client registration and assistant object creation.
KeyLoad Safeguard: Never worry about how many people use your iPhone4S key. Each Key has a maximum keyload. Even when the key is still valid, if the keyload limit is exceeded, the safeguard disables the key and protects the iPhone4S from getting banned.
KeyLoad Aware: Checks what key is not "Hot" anymore and periodically decreases the load, thus re-enabling Safeguarded Keys
Web interface and monitoring: Always know what is happening without a CLI! With a web interface you can check statistics such as active connections, valid keys, server load, keyload etc.
One certificate for all devices: Both Siri Capable devices (currently only iPhone4s) and older devices are using the same certificate and the same port (443 default for SSL)
One instance of the server: Due to one certificate you can run only one instance of the server.
Bug Free (I hope...):-) Never worry if the server has crashed. Most of the bugs that were causing the server to crash are fixed now.

Intro and how it works

This server uses a very simple but clever and precatius tactic to server a larger number of devices and at the same time protects the key.

I editing and forked @kmsbueromoebel 's server just because Apple followed a very bad tactic. That was Siri assistant software restriction to older devices, done only for marketing reason (my humble opinion).

So lets get to the point how does this work?

Step 1:

Lets say two Siri Capable Devices (currently only iPhone4s) connect to server. The server saves the keys on the Database.

Each key has assistantid,speechid, sessionValidationData,expired,keyload and date_added columns. Lets see what they are about:

assistantid - The assistant identifier. Unique for each device. In other words this defines your Siri and how it responds. eg. If I gave you my assistantid then Siri would get confused and sometimes respond to you with my nickname. Ugly.
Although it's stored on the database its not used. Each older device that connects on the server creates a new assistantid via using the sessionValidationData.
speechid - The speech identifier. Again unique for each device like above.
sessionValidationData - The most importand field and the only thing needed for using siri on older devices. These validation data is a big string that gets generated every 24 hours on Siri Capable Devices via FairPlayed. These validation data allow only a small number of assistant's to be created and are somehow linked to the original Siri Capable Device
expired - It changed to true when the sessionValidation Data (mentioned above) expire. Default value="False" as enum
keyload - How much the key has been used. The default values is 0 and the maximum value is 1000. Each time a device connects and makes a session the keyload increases by 10. So each key can serve up to 100 connection sessions until it gets overloaded and pauses up for a period of time

Ok the keys are saved what now?

Each time a older device connects, the server finds the key with the least keyload and uses that to forge the packets with the sessionValidationData in order to be accepted by guzzoni.apple.com (Apple's siri servers)
Each older device that connects uses the sessionValidationData to create a assistant.
After the assistant is created it can use siri via the proxy for speech recognition and views creation.
When one of the keys are overloaded (reaches the keyload max values) the server then does not forge the packets thus stops misusement of the key.
After 15 minutes of the overloaded key drops -100 lets another 10 sessions to be created and so on until the key expires.
This helps a lot to pretend that its a normal everyday use (with some finetuning to the above values and limits) and spoofing/securing the Siri Capable Devices.
Also a webgui can help you monitor the active concurrent connections, and all the above in realtime. You can forget ssh'ing to your VPS and using screen to view how the server is doing.

Tutorial: Get the Pigs Up and Running

For a tutorial please refer to my github here

Enjoy!!!!!

That's it. If you like this project please support my work and others work by donations.

Dont forget to say a big thanks to @WouterDS who created the web-interface and @thpryrchn for the rake and gem guide

Credits,greetings and big thanks to all the following... (in line of order)
RESPECT

Quartz Coding

Siri Validation Data and Access Token