Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Re:Nothing on Facebook is private (Score 2) 593

That's beside the point. Here you have a trained killer threatening to severe heads with an axe. I don't know if it's a crime per se, but it's something the government would be held liable if they don't investigate. The truth is that there are a lot of nutjobs, but when you have trained person threatening to use such training to attack the government it would be irresponsible not to act.

Facebook is forced by law to monitor and report on such activities. This is non news.

Comment 100% of the congress approved this law ... (Score 2) 828

... including Chavez supporters and ALL THE OPOSITION. In fact, this is the ONLY issue, after 13 years, where both sides agree completely.

(sorry, posted as anonymous by mistake. this is not redundant)

It's very easy to have an opinion when you live in a first world country. But when you have experienced the level of violence on the streets (regardless of your support or not for the regime), this measure is like a (small) breath of air.

Our situation is very different than in other countries. In all my life I've seen, while walking on the street, 4 people get killed by gunshots. All of them robberies. How many people can claim to have witnessed that much crime while simply walking on the street? And the first one was when I was 10 years old ... long before Chavez.

Violence runs on the blood of the people here. It's a really sad state of affairs. You can be shot for not letting a car pass, or just looking at the wrong woman on the street.

I'm not saying that this is a perfect solution, or that this will solve all of our problems. This will not solve the deep problems that cause people to kill each other like nothing happened. But for once EVERYONE is at least trying, regardless of political views. And I really hope they succeed.

User Journal

Journal Journal: in which i am a noob all over again 17

I haven't posted a journal here in almost three years, because I couldn't find the button to start a new entry. ...yeah, it turns out that it's at the bottom of the page.

So... hi, Slashdot. I used to be really active here, but now I mostly lurk and read. I've missed you.

Comment Re:use? (Score 2, Funny) 59

They are using it to pump the economy. The heating produced by this cluster must be cooled with extra air conditioning systems, increasing the demand for power and for air conditioning unis, thus creating new jobs and incentivizing the research for new energy sources.

Submission + - ICANN to let thousands of TLDs bloom (latimes.com)

bigjocker writes: "According to the Los Angeles Times "The group that governs Internet domain names is opening up the system so that companies and organizations can apply to create their own versions of .com, .org or .gov. Under the new rules, instead of a coke.com, Coca-Cola might control the domain .coke and assign Web addresses such as drink.coke or bottle.coke". I don't know about you, but I'm getting in line to register snort.coke"

Comment Re:Might not be bad... (Score 3, Informative) 645

No, they not. That's the point of double hashing. If you know 'xyz' you still need to know 'opqr' to send a valid hash (remember that you need to hash 'xyz-opqr' with the session salt). Since the server never sends 'opqr' to the client, the only way to generate it is through HASH(xyz + plaintext_password).

Comment Re:Might not be bad... (Score 2) 645

This is nonsense. You can double hash passwords. That's the correct way:

plaintext: 1234
salt: xyz
salt+plaintext hash: opqr
you store on DB: xyz-opqr

when the user requests the login page, the server creates a new salt, stores it in the session (server side) and sends the two salts to the client (session one and DB one):

server extracts salt from DB: xyz
server creates a session salt: abc
client receives session salt: abc
client receives DB salt: xyz
user enters password: 1234
client hashes using DB salt: opqr
1st hash is: opqr
1st hash with salt is: xyz-opqr
client hashes using session salt: hijk
2nd hash is: hijk
client sends the twice hashed password to the server: hijk

Now the server hashes the DB password using the session salt (that was stored on the server side session, remember not to trust the info from the client), and the two should be the same, without the server needing to know the plaintext password.

This is basic auth and security stuff. Which means sony must have hired some second hand programmers to develop this whole system. Creepy indeed.

Slashdot Top Deals

Our OS who art in CPU, UNIX be thy name. Thy programs run, thy syscalls done, In kernel as it is in user!

Working...