Having spoken on this topic at a bunch of conferences (ChicagoCon, Defcon, RSA, Source, etc.), I'll weigh in:
Forget certifications until you know what you want to do.
Then, once you've figured out what you want to do, figure out whether you need certs to do it.
For example, if you want a job as a pen-tester, certs aren't generally going to help. Most pen-test consultancies (with a few exceptions) are smaller companies that hire based on knowing people and merit far more than "Oh, you have a CEH, welcome aboard". In that case, go out and start doing stuff. Join a CTF team at Defcon. If you're still in school, participate in CCDC. Get involved in your local community - OWASP meetings, (Linux/BSD/Mac/Windows) user groups, etc.
Get a CEH later if you feel like it, but it doesn't need to be about that.
(As an example: I've been pen testing for more than 10 years, have lead vuln research teams, have taught certification courses for CEH/ECSA/CEPT and don't have a CEH.)
The bigger question - why do you want to be in security? What do you love about it? And what part of it do you find yourself being good at as you read about it and work on it in your spare time?







Gates : Isabelle Marant if you're|a really wonderful|pc|whether you are having a lesson




