Federico Biancuzzi: Disclosure survey
543979
Disclosure survey &gt;&gt; Advertisement &lt;&lt;  ALERT: "How A Hacker Launches A Blind SQL Injection Attack Step-by-Step"!" - White Paper  Blind SQL Injection can deliver total control of your server to a hacker giving them the ability to read, write and manipulate all data stored in your backend systems! Download this *FREE* white paper from SPI Dynamics for a complete guide to protection! https://download.spidynamics.com/1/ad/bsq.asp?Campaign_ID=701600000004c29
264512
"Da verificare quanta parte del gettito sara' strutturale"
37464
Diffata Mediaset, immagini consentono identificazione
244431
'Preoccupanti' i dati diffusi dall'Istat sulle retribuzioni
357182
In a new post to his blog, Chris Hartjes, spurred on by an article in the latest edition of php|architect magazine (covering protecting your code), has shared a few opinions starting with a certain paragraph near the end.   To start, I will focus on the paragraph above. What I get out of that is that if only your source was closed and hidden from prying eyes, it would not have bugs in it. Which is, of course, total nonsense. Code has bugs because it's open and they feel safer? There are two kinds of bugs: application bugs (which is the code I would write) and system bugs (in this case, bugs that that appear from PHP itself). I'm sorry, but there is nothing I can do if there is a bug in PHP that causes my application to crash except to point this bug out to the people who have the ability to fix it.   He goes on to talk more about how protection like this (the article talks about using the IonCube Encoder) will not stop someone if they're really determine to get at the code underneath the encryption. His only suggestion is to make an application good enough that people wouldn't want to try to steal it as much and would rather pay for their version.   Encode your stuff if you want, but be aware that the minute you choose to do that you are telling your customers "I don't trust you" and I have a hard time understanding a business model that assumes people are going to want to steal the stuff you sell.
86959
An inside look at the elaborate secrecy campaign around the biggest book of all time
648704
Tra le notizie piÃ¹ interessanti del secondo giorno di lavori di Idf (Intel Developer Forum) che si sta svolgendo a S. Francisco, ci sono quelle sulle prossime piattaforme per portatili. Anand Chandrasekher
662242
'L'Autorita' denunci la criticita' del sistema'
363515
L'attribuzione decisa dal Presidente della Repubblica
484932
Nelson Minar says he likes TechCrunch, but they're not journalists so be careful what you say to a TC reporter at a party. He cites two examples where he feels they acted unethically.  In one example, the reporter seems to use off the record comments exactly as they are supposed to. Most non-disclosures require that you keep the information confidential, but only until someone else discloses the information to you. If you get it from another source, on the record or off the record, the NDA is no longer enforceable. In this case they got confirmation from three off the record sources.  The other is just an example of a dumb story, not a violation of journalistic ethics. To say that a big company told a lie is hardly news. If it were about something material and not the age of one of the founders, then it would be newsworthy. But it's not an example of an integrity breach. (You can make a mistake and still have integrity. It's only a problem if you knew it was wrong when you wrote it.) Imho, too much is made of whether someone is a journalist or not. You read reports like this one in a highly reputed news organization, written by a journalist, that contain no information but leave a sensational impression for people who don't know the technology well enough to know that the reporter is talking nonsense. I'd rather read the opinion of a non-journalist who knows the subject and can defend his or her position, and clearly discloses their interest in the subject. At least I'd learn something, and no one would be misled into believing they were getting "news." However I do applaud what Nelson wrote because he had the guts to openly criticize TechCrunch. People from outside Silicon Valley must wonder why hardly anyone does, given that they are at or near the top of most lists ranking tech news sources. Why should they be immune to examination? Answer -- they shouldn't.
196894
Erano accatastate come studi privati, una denuncia
424613
La posta elettronica di Kataweb cambia look, si arricchisce di nuove funzioni e aumenta lo spazio a disposizione. Due potenti funzioni antivirus e antispam garantiscono la sicurezza degli utenti e dei dati e un calendario personale permette di tenere gli impegni sotto controllo. Apri la tua casella ora, &egrave; gratuita!
440364
Le moderne tecnologie informatiche consentono di avvicinare sempre di piÃ¹ il mondo giudiziario all&#39;avvocatura. In linea con questo progresso e sensibili alle esigenze della Magistratura e dell&#39;Avvocatura
628082
Unita' di crisi ne sta verificando autenticita' e data
303065
Ziff Davis - There are lots of good reasons for 'net anonymity.
179730
Su denuncia delle vittime, proposto pizzo "a rate"
62130
In response to a previous article from the Symfony blog, Paul Jones has pulled together some thoughts to some of the comments they made.   As the author of a relatively popular benchmarking article, I feel compelled to respond to this bit of misguided analysis from the Symfony camp about benchmarks.   Paul talks about the "straw-man arguments" presented in the Symfony article, including some references to Paul's previous benchmarks. He's even broken it down into a point-by-point response to make each point clear.