<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" xml:lang="en" xml:base="http://blog.codelime.net/wp-atom.php">
	<title type="text">blog.codelime.net</title>
	<subtitle type="text" />

	<updated>2012-05-11T14:19:28Z</updated>

	<link rel="alternate" type="text/html" href="http://blog.codelime.net" />
	<id>http://blog.codelime.net/feed/atom</id>
	

	<generator uri="http://wordpress.org/" version="3.3.2">WordPress</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/blog-codelime" /><feedburner:info uri="blog-codelime" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[Come gestire correttamente gli errori 404 Not Found]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/bksK8Kc2yHQ/come-gestire-correttamente-gli-errori-404-not-found.html" />
		<id>http://blog.codelime.net/?p=221</id>
		<updated>2012-05-11T14:19:28Z</updated>
		<published>2012-05-11T14:16:37Z</published>
		<category scheme="http://blog.codelime.net" term="SysAdmin" /><category scheme="http://blog.codelime.net" term="Web" /><category scheme="http://blog.codelime.net" term="404" /><category scheme="http://blog.codelime.net" term="Pagine di Errore" /><category scheme="http://blog.codelime.net" term="Webserver" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2012/05/11/come-gestire-correttamente-gli-errori-404-not-found.html#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2012/05/11/come-gestire-correttamente-gli-errori-404-not-found.html/feed/atom" thr:count="0" />
		<thr:total>0</thr:total>
	<content type="html">Questo più che un articolo è un suggerimento su come gestire gli errori 404 Not Found nei webserver, che altro non sono che le pagine che i webserver visualizzano quando viene richiesto un URL non presente nel webserver. Questo sito moldavo ci da una lezione su come le pagine di errore dovrebbero esser gestite all&amp;#8217;epoca&amp;#8230;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/tiz6CccnIl7diXOuls2hgBbN8v8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tiz6CccnIl7diXOuls2hgBbN8v8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/tiz6CccnIl7diXOuls2hgBbN8v8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tiz6CccnIl7diXOuls2hgBbN8v8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/bksK8Kc2yHQ" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2012/05/11/come-gestire-correttamente-gli-errori-404-not-found.html</feedburner:origLink></entry>
		<entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[Proteggere i server con DirectAdmin da attacchi SlowHTTP/Slowloris]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/97YSYWrbCyE/proteggere-i-server-con-directadmin-da-attacchi-slowhttpslowloris.html" />
		<id>http://blog.codelime.net/?p=217</id>
		<updated>2012-01-31T17:06:28Z</updated>
		<published>2012-01-31T17:05:44Z</published>
		<category scheme="http://blog.codelime.net" term="Linux" /><category scheme="http://blog.codelime.net" term="SysAdmin" /><category scheme="http://blog.codelime.net" term="Web" /><category scheme="http://blog.codelime.net" term="Apache" /><category scheme="http://blog.codelime.net" term="DirectAdmin" /><category scheme="http://blog.codelime.net" term="mod_antiloris" /><category scheme="http://blog.codelime.net" term="SlowHTTP" /><category scheme="http://blog.codelime.net" term="SlowLoris" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2012/01/31/proteggere-i-server-con-directadmin-da-attacchi-slowhttpslowloris.html#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2012/01/31/proteggere-i-server-con-directadmin-da-attacchi-slowhttpslowloris.html/feed/atom" thr:count="0" />
		<thr:total>0</thr:total>
	<content type="html">Gli attacchi del tipo SlowHTTP/Slowloris sono tra i più fastidiosi da ricevere in quanto il server di per sè non riporta nessuna anomalia se non un elevato numero di processi attivo, ma senza carico effettivo sulla macchina, questo perchè l&amp;#8217;attacco apre quante più connessioni possibili al webserver e le lascia aperte inviando saltuariamente qualche header&amp;#8230;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/jZZuOsQQfWrBo9whwGGdgZwOUog/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jZZuOsQQfWrBo9whwGGdgZwOUog/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/jZZuOsQQfWrBo9whwGGdgZwOUog/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jZZuOsQQfWrBo9whwGGdgZwOUog/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/97YSYWrbCyE" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2012/01/31/proteggere-i-server-con-directadmin-da-attacchi-slowhttpslowloris.html</feedburner:origLink></entry>
		<entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[Proteggere il proprio server dagli attacchi brute force con APF e BFD]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/BHMK__A_VNQ/proteggere-il-proprio-server-dagli-attacchi-brute-force-con-apf-e-bfd.html" />
		<id>http://blog.codelime.net/?p=210</id>
		<updated>2011-10-24T17:24:50Z</updated>
		<published>2011-10-24T17:24:50Z</published>
		<category scheme="http://blog.codelime.net" term="Linux" /><category scheme="http://blog.codelime.net" term="SysAdmin" /><category scheme="http://blog.codelime.net" term="brute force" /><category scheme="http://blog.codelime.net" term="Debian" /><category scheme="http://blog.codelime.net" term="proteggere" /><category scheme="http://blog.codelime.net" term="server" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2011/10/24/proteggere-il-proprio-server-dagli-attacchi-brute-force-con-apf-e-bfd.html#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2011/10/24/proteggere-il-proprio-server-dagli-attacchi-brute-force-con-apf-e-bfd.html/feed/atom" thr:count="0" />
		<thr:total>0</thr:total>
	<content type="html">Usare password lunghe e complesse spesso non è sufficiente a proteggere il proprio server da eventuali intrusioni, per questo oggi spieghiamo come proteggerlo da attacchi di tipo brute force utilizzando due semplici software che sfruttano il firewall iptables. Questi due software vengono distribuiti gratuitamente dal sito http://www.rfxn.com/, ora andiamo a vedere nel dettaglio cosa fanno e&amp;#8230;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/gs2SevLRx9ZXII54XOsHyxX3nrE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/gs2SevLRx9ZXII54XOsHyxX3nrE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/gs2SevLRx9ZXII54XOsHyxX3nrE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/gs2SevLRx9ZXII54XOsHyxX3nrE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/BHMK__A_VNQ" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2011/10/24/proteggere-il-proprio-server-dagli-attacchi-brute-force-con-apf-e-bfd.html</feedburner:origLink></entry>
		<entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[SSH Client &#8211; evitare i broken pipe]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/s8I-o9qlsKw/ssh-client-evitare-i-broken-pipe.html" />
		<id>http://blog.codelime.net/?p=206</id>
		<updated>2011-05-27T08:05:09Z</updated>
		<published>2011-05-27T08:04:41Z</published>
		<category scheme="http://blog.codelime.net" term="Linux" /><category scheme="http://blog.codelime.net" term="Tips" /><category scheme="http://blog.codelime.net" term="Borken Pipe" /><category scheme="http://blog.codelime.net" term="SSH" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2011/05/27/ssh-client-evitare-i-broken-pipe.html#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2011/05/27/ssh-client-evitare-i-broken-pipe.html/feed/atom" thr:count="0" />
		<thr:total>0</thr:total>
	<content type="html">Spesso accade che quando si è connessi in SSH ad un server la connessione si interrompe ritornando come errore &amp;#8220;Borken Pipe&amp;#8221;, questo perchè la connessione non ha un KeepAlive che la mantiene attiva, per evitare questo problema bisogna aggiungere la seguente riga al file /etc/ssh/ssh_config ServerAliveInterval 120
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/QHNNtdd2Bn87JKggk5OM_7RSERQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/QHNNtdd2Bn87JKggk5OM_7RSERQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/QHNNtdd2Bn87JKggk5OM_7RSERQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/QHNNtdd2Bn87JKggk5OM_7RSERQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/s8I-o9qlsKw" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2011/05/27/ssh-client-evitare-i-broken-pipe.html</feedburner:origLink></entry>
		<entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[Autocomplete per bash su Debian]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/hOvLSKhi50I/autocomplete-per-bash-su-debian.html" />
		<id>http://blog.codelime.net/?p=203</id>
		<updated>2011-05-27T07:50:35Z</updated>
		<published>2011-05-27T07:50:35Z</published>
		<category scheme="http://blog.codelime.net" term="Linux" /><category scheme="http://blog.codelime.net" term="Tips" /><category scheme="http://blog.codelime.net" term="Autocomplete" /><category scheme="http://blog.codelime.net" term="Bash" /><category scheme="http://blog.codelime.net" term="Debian" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2011/05/27/autocomplete-per-bash-su-debian.html#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2011/05/27/autocomplete-per-bash-su-debian.html/feed/atom" thr:count="0" />
		<thr:total>0</thr:total>
	<content type="html">Ecco un piccolo tip per chi come me ama l&amp;#8217;autocomplete nella shell bash, su debian non è abilitato per default, ma per attivarlo è sufficiente aggiungere a .bashrc la seguente riga source /etc/bash_completion salvare, fare logout e nuovamente login. Se non dovesse ancora funzionare controllate se esiste il file /etc/bash_completion (attenzione a non confonderlo con&amp;#8230;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/bMVuxFLHyID3eUna99idTch9Du0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/bMVuxFLHyID3eUna99idTch9Du0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/bMVuxFLHyID3eUna99idTch9Du0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/bMVuxFLHyID3eUna99idTch9Du0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/hOvLSKhi50I" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2011/05/27/autocomplete-per-bash-su-debian.html</feedburner:origLink></entry>
		<entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[H3G chiude Skype per X-Series]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/Rt4WOVgQmmc/h3g-chiude-skype-per-x-series.html" />
		<id>http://blog.codelime.net/?p=195</id>
		<updated>2011-03-29T08:38:34Z</updated>
		<published>2011-02-24T17:45:27Z</published>
		<category scheme="http://blog.codelime.net" term="Android" /><category scheme="http://blog.codelime.net" term="Smartphone" /><category scheme="http://blog.codelime.net" term="Telefonia" /><category scheme="http://blog.codelime.net" term="H3G" /><category scheme="http://blog.codelime.net" term="Skype" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2011/02/24/h3g-chiude-skype-per-x-series.html#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2011/02/24/h3g-chiude-skype-per-x-series.html/feed/atom" thr:count="0" />
		<thr:total>0</thr:total>
	<content type="html">Con un comunicato via sms e web H3G ufficializza la chiusura definitiva del servizio Skype per X-Series il 27 marzo 2011, il servizio in questione permetteva di effettuare chiamate skype non via rete WiFi o 3G ma attraverso un tunneling telefonico, garantendo così una qualità di chiamata decisamente superiore. Ecco il comunicato di H3G: Ti&amp;#8230;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Hihm_oST_HWwCwVT7AI7sYuhhRY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Hihm_oST_HWwCwVT7AI7sYuhhRY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Hihm_oST_HWwCwVT7AI7sYuhhRY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Hihm_oST_HWwCwVT7AI7sYuhhRY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/Rt4WOVgQmmc" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2011/02/24/h3g-chiude-skype-per-x-series.html</feedburner:origLink></entry>
		<entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[Vulnerabilità XSS per WordPress 3.0.3]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/irgXiwAfemM/vulnerabilita-xss-per-wordpress-3-0-3.html" />
		<id>http://blog.codelime.net/?p=191</id>
		<updated>2010-12-29T23:13:28Z</updated>
		<published>2010-12-29T23:13:28Z</published>
		<category scheme="http://blog.codelime.net" term="Wordpress" /><category scheme="http://blog.codelime.net" term="bug" /><category scheme="http://blog.codelime.net" term="fix" /><category scheme="http://blog.codelime.net" term="XSS" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2010/12/30/vulnerabilita-xss-per-wordpress-3-0-3.html#comments" thr:count="2" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2010/12/30/vulnerabilita-xss-per-wordpress-3-0-3.html/feed/atom" thr:count="2" />
		<thr:total>2</thr:total>
	<content type="html">Oggi pomeriggio è stato svelato un nuovo bug relativo all&amp;#8217;ultima versione di wordpress documentato al seguente link http://bugsearch.net/it/11185/wordpress-303-stored-xss-ie76-ns81.html Prontamente il team di wordpress stasera ha rilasciato la nuova versione 3.0.4 che risolve il bug ma sfortunatamente ad ora è disponibile solo in lingua inglese, per tutti gli utenti con wordpress localizzato in altre lingue consiglio&amp;#8230;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/F1HpQsZZ77YQWqy9-iNKxBG52lg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/F1HpQsZZ77YQWqy9-iNKxBG52lg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/F1HpQsZZ77YQWqy9-iNKxBG52lg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/F1HpQsZZ77YQWqy9-iNKxBG52lg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/irgXiwAfemM" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2010/12/30/vulnerabilita-xss-per-wordpress-3-0-3.html</feedburner:origLink></entry>
		<entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[Tastiera Gingerbread su Foryo ed Eclair grazie a XDA-developers]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/4_yojc6p9Wk/tastiera-gingerbread-su-foryo-ed-eclair-grazie-a-xda-developers.html" />
		<id>http://blog.codelime.net/?p=186</id>
		<updated>2010-12-23T11:44:12Z</updated>
		<published>2010-12-23T11:44:12Z</published>
		<category scheme="http://blog.codelime.net" term="Android" /><category scheme="http://blog.codelime.net" term="Gingerbread" /><category scheme="http://blog.codelime.net" term="Tastiera" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2010/12/23/tastiera-gingerbread-su-foryo-ed-eclair-grazie-a-xda-developers.html#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2010/12/23/tastiera-gingerbread-su-foryo-ed-eclair-grazie-a-xda-developers.html/feed/atom" thr:count="0" />
		<thr:total>0</thr:total>
	<content type="html">Stamattina ho trovato su xda-developers un porting della tastiera del nuovo Android Gingerbread per Froyo e Eclair. A dire il vero ne ho trovate più di una, ma le seguenti due sono le più interessanti perchè non necessitano di root e quindi chiunque le può installare. Prima di passare ai link per il download diamo&amp;#8230;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/dQD6TEjGfD6zIuhB6mUQQf5rVRc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/dQD6TEjGfD6zIuhB6mUQQf5rVRc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/dQD6TEjGfD6zIuhB6mUQQf5rVRc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/dQD6TEjGfD6zIuhB6mUQQf5rVRc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/4_yojc6p9Wk" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2010/12/23/tastiera-gingerbread-su-foryo-ed-eclair-grazie-a-xda-developers.html</feedburner:origLink></entry>
		<entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[Vodafone Ideos: uno smartphone android entry level]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/EVW4ZFibSDg/vodafone-ideos-uno-smartphone-android-entry-level.html" />
		<id>http://blog.codelime.net/?p=174</id>
		<updated>2010-12-20T16:33:59Z</updated>
		<published>2010-12-20T16:33:20Z</published>
		<category scheme="http://blog.codelime.net" term="Android" /><category scheme="http://blog.codelime.net" term="Smartphone" /><category scheme="http://blog.codelime.net" term="Froyo" /><category scheme="http://blog.codelime.net" term="Huawei" /><category scheme="http://blog.codelime.net" term="Ideos" /><category scheme="http://blog.codelime.net" term="Vodafone" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2010/12/20/vodafone-ideos-uno-smartphone-android-entry-level.html#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2010/12/20/vodafone-ideos-uno-smartphone-android-entry-level.html/feed/atom" thr:count="0" />
		<thr:total>0</thr:total>
	<content type="html">Vodafone ha da poco messo in offerta lo smartphone Ideos della Huawei a 99€ con inclusa una ricaricabile con 5€ di traffico incluso, oppure a 0€ con abbonamento. Ne ho comprato uno sabato e devo dire che ne sono veramente soddisfatto. Guardando le specifiche del telefono non sembra niente male per essere un entry level,&amp;#8230;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/8XCEcQ-6kWmPSbGBMR_NXHy2HdE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8XCEcQ-6kWmPSbGBMR_NXHy2HdE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/8XCEcQ-6kWmPSbGBMR_NXHy2HdE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/8XCEcQ-6kWmPSbGBMR_NXHy2HdE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/EVW4ZFibSDg" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2010/12/20/vodafone-ideos-uno-smartphone-android-entry-level.html</feedburner:origLink></entry>
		<entry>
		<author>
			<name>admin</name>
					</author>
		<title type="html"><![CDATA[Froyo per HTC Wildfire disponibile]]></title>
		<link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blog-codelime/~3/NPQL2Fss56g/froyo-per-htc-wildfire-disponibile.html" />
		<id>http://blog.codelime.net/?p=176</id>
		<updated>2010-12-20T09:56:21Z</updated>
		<published>2010-12-20T09:17:41Z</published>
		<category scheme="http://blog.codelime.net" term="Android" /><category scheme="http://blog.codelime.net" term="Smartphone" /><category scheme="http://blog.codelime.net" term="Froyo" /><category scheme="http://blog.codelime.net" term="HTC" /><category scheme="http://blog.codelime.net" term="Wildfire" />		
		<link rel="replies" type="text/html" href="http://blog.codelime.net/2010/12/20/froyo-per-htc-wildfire-disponibile.html#comments" thr:count="4" />
		<link rel="replies" type="application/atom+xml" href="http://blog.codelime.net/2010/12/20/froyo-per-htc-wildfire-disponibile.html/feed/atom" thr:count="4" />
		<thr:total>4</thr:total>
	<content type="html">Da qualche minuto è stato reso finalmente disponibile l&amp;#8217;aggiornamento a FroYo anche per HTC Wildfire, da stamattina era iniziato il processo di aggiornamento in europa, e stato per stato lo stanno rilasciando. Prima di fare l&amp;#8217;update controllate sempre di avere la connessione flat o wifi, sono circa 60Mb di download. L&amp;#8217;aggiornamento è OTA quindi basta&amp;#8230;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/9PWR1IvJK_Rzrogz0vL77PBr2N8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/9PWR1IvJK_Rzrogz0vL77PBr2N8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/9PWR1IvJK_Rzrogz0vL77PBr2N8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/9PWR1IvJK_Rzrogz0vL77PBr2N8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/blog-codelime/~4/NPQL2Fss56g" height="1" width="1"/&gt;</content><feedburner:origLink>http://blog.codelime.net/2010/12/20/froyo-per-htc-wildfire-disponibile.html</feedburner:origLink></entry>
	</feed>

