Ebbene sì, nuovo post sulla pagina di Facebook degli hacker: Si rinvia ancora il rilascio del porting… Anzi non era mai stato programmato!
Infatti il team cinese ha comunicato oggi che c’era stato un errore di traduzione in Europa!
Ecco il post originale:
“We have made a translation error (contact in Europe), we do not give H1-Siri, 1.0, before the release of the jailbreak A5 as it would be useless because there would be no connection.
We apologize for the inconvenience”
Traduzione: “Abbiamo fatto un errore di traduzione (ai contatti europei), non rilasceremo H1-Siri, 1.0, prima del rilascio del jailbreak A5 dato che sarebbe inutile vista l’assenza di connessione. Ci scusiamo per l’inconveniente”
La domanda che sorge spontanea è quindi: “Ma sarà davvero un errore di traduzione o un problema con il tweak?!”.
Non manca molto alla risposta, infatti tra pochi giorni verrà rilasciato il jailbreak per gli idevices che montano il processore A5 e scopriremo la verità.
Vi terremo aggiornati, Stay Tuned!
Samuele Panzeri
Loading ...
Autore chi pubblica o chi scrive l’articolo?
Saluti sia a Samu che a Eva
Quando c’è il mio nome è perchè l’ho scritto io (;
TEST
io credo e continuo a ribadire la mia posizione…se così la posso chiamare….verrà eventualmente rilasciato il porting di siri su gli altri device….ma il problema rimarrà sempre lo stesso…si andrà a compromettere una battaglia che si è già vinto….in USA il jb è legale…quindi ora effettuando un porting di SIRI….il tutto potrebbe diventare illegale….per violazione de copyright….(come tutti dovreste sapere…apple ha depositato alcuni brevetti di siri…..brevetti le cui caratteristiche non vengono viste o non vengono utilizzate…una di queste è proprio la violazione o l’emulazione di siri su dispositivi non registrati in brevetto…quindi solo il 4s è registrato in brevetto…il tutto verrò dichiarato illegalmente al suo rilascio….ovviamente chi avrà permesso l’appoggio a questo…?SAURIK CON IL SUO CYDIA….IL QUALEstranamente non ha saputo prendere ancora una posizione in merito….questo vuol dire che sta per buttare all’aria anni e anni di lotte e battaglie..sia legali che non..per cosa…???? per uno stupido assistente che ti butta giù la batteria e ti consuma più di 100 mb al mese?….su via diciamocelo onestamente….di SIRI ne abbiamo fatto a meno per 2011 anni….e cmq siamo riusciti a sopravvivere…..figuriamoci oggi….!
Antonio
Antonio ho scritto questo articolo puramente a scopo informativo e comunque dal mio punto di vista il tweak non verra rilasciato presto! Questi cinesi hanno paura di ripetere l’errore e far uscire nuovamente una versione illegale!
Quello che mi chiedo è se è possibile che Apple abbia permesso apposta di usare dei file di Siri sapendo che questo è illegale su altri devices e quindi rendere poi completamente illegale il jailbreak!
Dovrebbe essere questo lo script OPENSSL
#
# OpenSSL example configuration file.
# This is mostly being used for generation of certificate requests.
#
# This definition stops the following lines choking if HOME isn’t
# defined.
HOME = .
RANDFILE = $ENV::HOME/.rnd
# Extra OBJECT IDENTIFIER info:
#oid_file = $ENV::HOME/.oid
oid_section = new_oids
# To use this configuration file with the “-extfile” option of the
# “openssl x509″ utility, name here the section containing the
# X.509v3 extensions to use:
# extensions =
# (Alternatively, use a configuration file that has only
# X.509v3 extensions in its main [= default] section.)
[ new_oids ]
# We can add new OIDs in here for use by ‘ca’, ‘req’ and ‘ts’.
# Add a simple OID like this:
# testoid1=1.2.3.4
# Or use config file substitution like this:
# testoid2=${testoid1}.5.6
# Policies used by the TSA examples.
tsa_policy1 = 1.2.3.4.1
tsa_policy2 = 1.2.3.4.5.6
tsa_policy3 = 1.2.3.4.5.7
####################################################################
[ ca ]
default_ca = CA_default # The default ca section
####################################################################
[ CA_default ]
dir = /tmp/siriCA # Where everything is kept
certs = $dir/certs # Where the issued certs are kept
crl_dir = $dir/crl # Where the issued crl are kept
database = $dir/index.txt # database index file.
#unique_subject = no # Set to ‘no’ to allow creation of
# several ctificates with same subject.
new_certs_dir = $dir/newcerts # default place for new certs.
certificate = $dir/cacert.pem # The CA certificate
serial = $dir/serial # The current serial number
crlnumber = $dir/crlnumber # the current crl number
# must be commented out to leave a V1 CRL
crl = $dir/crl.pem # The current CRL
private_key = $dir/private/cakey.pem# The private key
RANDFILE = $dir/private/.rand # private random number file
x509_extensions = usr_cert # The extentions to add to the cert
# Comment out the following two lines for the “traditional”
# (and highly broken) format.
name_opt = ca_default # Subject Name options
cert_opt = ca_default # Certificate field options
# Extension copying option: use with caution.
# copy_extensions = copy
# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs
# so this is commented out by default to leave a V1 CRL.
# crlnumber must also be commented out to leave a V1 CRL.
# crl_extensions = crl_ext
default_days = 365 # how long to certify for
default_crl_days= 30 # how long before next CRL
default_md = sha1 # use public key default MD
preserve = no # keep passed DN ordering
# A few difference way of specifying how similar the request should look
# For type CA, the listed attributes must be the same, and the optional
# and supplied fields are just that
policy = policy_match
# For the CA policy
[ policy_match ]
countryName = match
stateOrProvinceName = match
organizationName = match
organizationalUnitName = optional
commonName = supplied
emailAddress = optional
# For the ‘anything’ policy
# At this point in time, you must list all acceptable ‘object’
# types.
[ policy_anything ]
countryName = optional
stateOrProvinceName = optional
localityName = optional
organizationName = optional
organizationalUnitName = optional
commonName = supplied
emailAddress = optional
####################################################################
[ req ]
default_bits = 1024
default_keyfile = privkey.pem
distinguished_name = req_distinguished_name
attributes = req_attributes
x509_extensions = v3_ca # The extentions to add to the self signed cert
default_md = sha1
# Passwords for private keys if not present they will be prompted for
# input_password = secret
# output_password = secret
# This sets a mask for permitted string types. There are several options.
# default: PrintableString, T61String, BMPString.
# pkix : PrintableString, BMPString (PKIX recommendation before 2004)
# utf8only: only UTF8Strings (PKIX recommendation after 2004).
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
# MASK:XXXX a literal mask value.
# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.
string_mask = utf8only
# req_extensions = v3_req # The extensions to add to a certificate request
[ req_distinguished_name ]
countryName = Country Name (2 letter code)
countryName_default = AU
countryName_min = 2
countryName_max = 2
stateOrProvinceName = State or Province Name (full name)
stateOrProvinceName_default = Some-State
localityName = Locality Name (eg, city)
0.organizationName = Organization Name (eg, company)
0.organizationName_default = Internet Widgits Pty Ltd
# we can do this but it is not needed normally
#1.organizationName = Second Organization Name (eg, company)
#1.organizationName_default = World Wide Web Pty Ltd
organizationalUnitName = Organizational Unit Name (eg, section)
#organizationalUnitName_default =
commonName = Common Name (eg, YOUR name)
commonName_max = 64
emailAddress = Email Address
emailAddress_max = 64
# SET-ex3 = SET extension number 3
[ req_attributes ]
challengePassword = A challenge password
challengePassword_min = 4
challengePassword_max = 20
unstructuredName = An optional company name
[ usr_cert ]
# These extensions are added when ‘ca’ signs a request.
# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.
basicConstraints=CA:FALSE
# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.
# This is OK for an SSL server.
# nsCertType = server
# For an object signing certificate this would be used.
# nsCertType = objsign
# For normal client use this is typical
# nsCertType = client, email
# and for everything including object signing:
# nsCertType = client, email, objsign
# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment
# This will be displayed in Netscape’s comment listbox.
nsComment = “OpenSSL Generated Certificate”
# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer
# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren’t
# deprecated according to PKIX.
# subjectAltName=email:move
# Copy subject details
# issuerAltName=issuer:copy
#nsCaRevocationUrl = http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName
# This is required for TSA certificates.
# extendedKeyUsage = critical,timeStamping
[ v3_req ]
# Extensions to add to a certificate request
basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
[ v3_ca ]
# Extensions for a typical CA
# PKIX recommendation.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer
# This is what PKIX recommends but some broken software chokes on critical
# extensions.
#basicConstraints = critical,CA:true
# So we do this instead.
basicConstraints = CA:true
# Key usage: this is typical for a CA certificate. However since it will
# prevent it being used as an test self-signed certificate it is best
# left out by default.
# keyUsage = cRLSign, keyCertSign
# Some might want this also
# nsCertType = sslCA, emailCA
# Include email address in subject alt name: another PKIX recommendation
# subjectAltName=email:copy
# Copy issuer details
# issuerAltName=issuer:copy
# DER hex encoding of an extension: beware experts only!
# obj=DER:02:03
# Where ‘obj’ is a standard or added object
# You can even override a supported extension:
# basicConstraints= critical, DER:30:03:01:01:FF
[ crl_ext ]
# CRL extensions.
# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.
# issuerAltName=issuer:copy
authorityKeyIdentifier=keyid:always
[ proxy_cert_ext ]
# These extensions should be added when creating a proxy certificate
# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.
basicConstraints=CA:FALSE
# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.
# This is OK for an SSL server.
# nsCertType = server
# For an object signing certificate this would be used.
# nsCertType = objsign
# For normal client use this is typical
# nsCertType = client, email
# and for everything including object signing:
# nsCertType = client, email, objsign
# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment
# This will be displayed in Netscape’s comment listbox.
nsComment = “OpenSSL Generated Certificate”
# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer
# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren’t
# deprecated according to PKIX.
# subjectAltName=email:move
# Copy subject details
# issuerAltName=issuer:copy
#nsCaRevocationUrl = http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName
# This really needs to be in place for it to be a proxy certificate.
proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo
####################################################################
[ tsa ]
default_tsa = tsa_config1 # the default TSA section
[ tsa_config1 ]
# These are used by the TSA reply generation only.
dir = ./demoCA # TSA root directory
serial = $dir/tsaserial # The current serial number (mandatory)
crypto_device = builtin # OpenSSL engine to use for signing
signer_cert = $dir/tsacert.pem # The TSA signing certificate
# (optional)
certs = $dir/cacert.pem # Certificate chain to include in reply
# (optional)
signer_key = $dir/private/tsakey.pem # The TSA private key (optional)
default_policy = tsa_policy1 # Policy if request did not specify it
# (optional)
other_policies = tsa_policy2, tsa_policy3 # acceptable policies (optional)
digests = md5, sha1 # Acceptable message digests (mandatory)
accuracy = secs:1, millisecs:500, microsecs:100 # (optional)
clock_precision_digits = 0 # number of digits after dot. (optional)
ordering = yes # Is ordering defined for timestamps?
# (optional, default: no)
tsa_name = yes # Must the TSA name be included in the reply?
# (optional, default: no)
ess_cert_id_chain = no # Must the ESS cert id chain be included?
# (optional, default: no)
E questo dovrebbe essere il generatore….
#!/usr/bin/env bash
commonName=$2
if [ "${commonName}" == "" ]
then
commonName=”SiriProxyCA”
fi
# Feel free to change any of these defaults
countryName=”US”
stateOrProvinceName=”Missouri”
localityName=”"
organizationName=”Siri Proxy”
organizationalUnitName=”"
emailAddress=”"
#You probably don’t need to modify these unless you know what you’re doing.
SIRI_PROXY_ROOT=$1
SIRI_PROXY_SETTINGS=~/.siriproxy
LOG_FILE=$SIRI_PROXY_SETTINGS/cert.log
TMP_DIR=/tmp
TMP_CA_DIR=/tmp/siriCA #THIS ($dir) ALSO MUST BE MODIFIED IN openssl.cnf IF YOU CHANGE IT!
## Do not edit below here!
echo “” > $LOG_FILE
echo “Creating CA directory”
mkdir -p $TMP_CA_DIR/{certs,crl,newcerts,private}
touch $TMP_CA_DIR/index.txt
echo 01 > $TMP_CA_DIR/crtnumber
echo “Generating ‘${commonName}’ CA request”
echo “${countryName}” > $TMP_DIR/ca.args
echo “${stateOrProvinceName}” >> $TMP_DIR/ca.args
echo “${localityName}” >> $TMP_DIR/ca.args
echo “${organizationName}” >> $TMP_DIR/ca.args
echo “${organizationalUnitName}” >> $TMP_DIR/ca.args
echo “${commonName}” >> $TMP_DIR/ca.args
echo “${emailAddress}” >> $TMP_DIR/ca.args
echo “” >> $TMP_DIR/ca.args
echo “” >> $TMP_DIR/ca.args
cat $TMP_DIR/ca.args | openssl req -new -config $SIRI_PROXY_ROOT/scripts/openssl.cnf -keyout $TMP_CA_DIR/private/cakey.pem -out $TMP_CA_DIR/careq.pem -passin pass:1234 -passout pass:1234 >> $LOG_FILE 2>> $LOG_FILE
echo “Self-signing ‘${commonName}’ CA”
openssl ca -create_serial -passin pass:1234 -config $SIRI_PROXY_ROOT/scripts/openssl.cnf -out $TMP_CA_DIR/cacert.pem -outdir $TMP_CA_DIR/newcerts -days 1095 -batch -keyfile $TMP_CA_DIR/private/cakey.pem -selfsign -extensions v3_ca -infiles $TMP_CA_DIR/careq.pem >> $LOG_FILE 2>> $LOG_FILE
echo “Generating guzzoni.apple.com certificate request”
echo “Generating ‘${commonName}’ CA request”
echo “${countryName}” > $TMP_DIR/ca.args
echo “${stateOrProvinceName}” >> $TMP_DIR/ca.args
echo “${localityName}” >> $TMP_DIR/ca.args
echo “${organizationName}” >> $TMP_DIR/ca.args
echo “${organizationalUnitName}” >> $TMP_DIR/ca.args
echo “guzzoni.apple.com” >> $TMP_DIR/ca.args
echo “${emailAddress}” >> $TMP_DIR/ca.args
echo “” >> $TMP_DIR/ca.args
echo “” >> $TMP_DIR/ca.args
cat $TMP_DIR/ca.args | openssl req -new -keyout $TMP_DIR/newkey.pem -config $SIRI_PROXY_ROOT/scripts/openssl.cnf -out $TMP_DIR/newreq.pem -days 1095 -passin pass:1234 -passout pass:1234 >> $LOG_FILE 2>> $LOG_FILE
echo “Generating guzzoni.apple.com certificate”
yes | openssl ca -policy policy_anything -out $TMP_DIR/newcert.pem -config $SIRI_PROXY_ROOT/scripts/openssl.cnf -passin pass:1234 -keyfile $TMP_CA_DIR/private/cakey.pem -cert $TMP_CA_DIR/cacert.pem -infiles $TMP_DIR/newreq.pem >> $LOG_FILE 2>> $LOG_FILE
echo “Removing passphrase from guzzoni.apple.com key”
yes | openssl rsa -in $TMP_DIR/newkey.pem -out $SIRI_PROXY_SETTINGS/server.passless.key -passin pass:1234 >> $LOG_FILE 2>> $LOG_FILE
echo “Cleaning up…”
mv $TMP_DIR/newcert.pem $SIRI_PROXY_SETTINGS/server.passless.crt
mv $TMP_CA_DIR/cacert.pem $SIRI_PROXY_SETTINGS/ca.pem
rm -rf $TMP_DIR/new{key,req}.pem $TMP_CA_DIR $TMP_DIR/ca.args
echo “Done! (For details on any errors, check ‘${LOG_FILE}’)”
echo “————————————————————-”
echo “”
echo “Please install ${SIRI_PROXY_SETTINGS}/ca.pem onto your phone!”
echo “(Note: You can do this by emailing the file to yourself)”
echo “”
echo “————————————————————-”
detto questo…vedrai quando uscirà….
l’anteprima?!
Secondo me Apple ha lasciato il codice sorgente aperto per chiudere e mettere definitivamente FINE alla questione JB….dimostrando che è ILLEGALE…e i risultati sono questi…il rilascio di un porting…che sarà sempre illegale…perchè tu puoi usare un proxy diverso….ma la sostanza e la violazione di copyright sarà sempre quella! VIOLAZIONE!
Sono d’accordo con te e spero che tu abbia capito lo scopo del mio articolo(informare) e sono contrario anche perchè da possessore di iPhone 4s mi da molto fastidio un possibile porting!