# Tag Info

6

Just to pile on to the great answers that are here, with something of a different angle. If you make the assumption that your v1 algorithm is going to be insecure and awful, and your v100 will be only very slightly better, but equally insecure. (as will your v1000) With that assumption in mind, you can learn a lot by solving the problems that ...

11

Bruce Schneier's Applied Cryptography is a must read if you want to start studying this field. I am surprised that nobody suggested it before. And yes, you need to know a lot about crypto even before trying to roll your own algorithms for fun. Don't even think of using them for real-world problems, though -- there's already a lot of bad crypto around. ...

2

Go ahead, write an algorithm but at the end give a task to one of your friends/fellows who regularly deal with cryptography; tell them to break your encryption if they can. You will notice that they will be able to break it in a matter of minutes and you'll be left stunned thinking as to how many loopholes were there that gave the game away to people with ...

2

You could follow Scott Wilson's suggestion about the One-Time pad, but with real random data. You can e.g. consider the noise from the computer's webcam. Let the webcam take a few pictures of a static scene, convert the images to 32 bit floating point images, normalize the pictures to the same brightness, take the average and then subtract one of the ...

2

You can implement already existing encryption algorithms, but designing your own encryption algorithm is one of the most complex matters you could deal with. For a general introduction I highly recommend this channel: https://www.youtube.com/channel/UC1usFRN4LCMcfIV7UjHNuQg/videos or the book "Understanding Cryptography" by Christoph Paar and Jan Pelzl ...

19

Start by breaking, not building your own. There's a worrisomely large number of stackexchange posts by people who've written their own algorithms. Take a look around and figure out what's wrong with them. (Don't look at the posted answers.) Only when you've found issues in other people's work should you move to trying to implement other people's ...

133

Of course you can start small and implement your own algorithms. But do not assume they provide any security beyond obfuscation. The difficult thing when it comes to cryptography is finding reasons why something actually is secure. You won't be able to decide that within months and if you feel like you are at that point, you are most probably wrong. It is ...

38

Coursera Here's my 2 cents: Join the Coursera Cryptography online class: Coursera: Stanford University, Professor Dan Boneh, Cryptography I The class takes six weeks. Each week there are several lecture videos, a graded quiz and an optional programming assignment. (And these assignments involve implementing crypto parts.) At the end of the six weeks ...

10

A good start would be to implement existing algorithms and learn how they work in depth. For example, the one-time pad algorithm is easy to learn and implement, and studying its strengths and weaknesses will get you started. It will also get you comfortable with the kind of bit-twiddling that's important in cryptography. Doing a search for "one-time pad" ...

1

As I understand, you control the input file /tmp/file and this piece of program is run with privileges to read a protected file. Your goal is to read the protected file. I failed to see any issue in this code. The format string is not controlled by the input and the missing line feeds you saw was because the last char of every 20 bytes is being replaced ...

0

The Italian company Hacking Team has job openings for hackers, see here: Hacker / Developer Developers design new features, develop them and polish our software to perfection. Hackers find out how to overcome the original design of objects, hack into them and uncover all their secrets. You have to be both, and the more you know, the better. We ...

1

Of course you can! Just follow a few guidelines and a SWAT team will not plant their boot on your neck at 3AM: Certified Ethical Hacker White Hat Hacker

1

My two cents worth of opinion: One becomes something by doing that particular kind of thing. In other words, one becomes a hacker, not by reading and talking about hacking, but by actual hacking. Likewise, one becomes a criminal by committing crimes. Therefore, it is clear that one might hack without committing crimes. So yes, one can be a hacker ...

14

There are many ways you can be an "ethical hacker." Here are a few that come to mind: You can write malware that helps catch the bad guys. Who the "bad guys" are may depend on who you're working for, and what your beliefs are. This may be a gray/black area to some. You can write malware so you can understand how it works, and then defend against it. The ...

1

You can get paid for finding vulnerabilities in software and web sites, that hackers could potentially exploit. For example, see here and here.

4

In many HSM, there is very little capacity for safe storage (say, a few kilobytes). Therefore, what the HSM really stores in its entrails is some master key K (symmetric). The key pairs that applications use are stored externally, but encrypted with K; they get decrypted and used only within the HSM. In such a setup, keys are both "logically" inside the HSM, ...

Top 50 recent answers are included