Become a fan of Slashdot on Facebook

 


Forgot your password?
Close
typodupeerror
User Journal

Journal Xerithane's Journal: OpenSSL: I beat you! 15

Journal by Xerithane

So, welcome back into the realm of technical discussions and my relay engine. I have the prototype running, and it runs like hot cakes. I mean fast, or something. The next step is allowing SSL connections, which seems slightly daunting because I've never worked with SSL/TSL and my first glance on the documentation caused my eyes to glaze over. Not because of complexity, but of horror. The documentation was horrible, and I think I've mentioned this before hand. The good news is is that after you figure out what the hell you are trying to do (which is amazingly unclear when starting the task of using SSL) it actually isn't so bad to find the documentation on the functions you may or may not need to use.

The next step of adding internal encryption on the bytestream is going to be exceptionally easy compared to the SSL portion. The SSL code was remarkably easy, had it been documented well. If they just included some sample code on how to accept an incoming SSL connection through a small httpd program, all would have been good in the world. I found Pound to be more descriptive in the SSL documentation than the actual documentation available on OpenSSL.

But, Victoly!

I know have my code relaying via SSL or not, and it still kicks ass. Happiness is mine!

This discussion has been archived. No new comments can be posted.

OpenSSL: I beat you! More

OpenSSL: I beat you!

Comments Filter:
  • ... victoly aside, can you stop exciting?
  • Congratulations on your success.

    Have you submitted any documentation or example suggestions to the OpenSSL team? They'd probably appreciate it, and other users certainly would. You know how programmers hate to document. ;)

    • Have you submitted any documentation or example suggestions to the OpenSSL team? They'd probably appreciate it, and other users certainly would. You know how programmers hate to document. ;)

      This software will go open source, under the Nerdfarm name. In there I'm going to write up a short little, "How to use OpenSSL in an application" document. My employer, while wanting to be anonymous, supports open source and is having a hidden partnership with Nerdfarm to release stuff open source. It works out very
      • It would probably help if you knew the difference between digests and block encryption, though.

        Have you figured it out yet? I liked the way you pussed out of your own challenge, by the way.
        • It would probably help if you knew the difference between digests and block encryption, though.

          Oh, and I'm sure that you can tell me which type SSL is? Go right ahead, I'm dying to hear it...

          Have you figured it out yet? I liked the way you pussed out of your own challenge, by the way.

          You are the one who backed out, dipshit.
          • Oh, and I'm sure that you can tell me which type SSL is? Go right ahead, I'm dying to hear it...

            Therefore, proving once again you don't have a clue what you are talking about ... you should read, say, the SSL/TLS spec.

            I think that's going in my quote file for you as well, "which type SSL is?". Where you honestly think the answer is that it uses either digest *or* block encryption. Hilarious.

            Here's a hint - look at the section on supported cipher suites in the spec. Now, what does it use for encryption o
            • Therefore, proving once again you don't have a clue what you are talking about ... you should read, say, the SSL/TLS spec.
              Actually I was expecting you to just be a retard again. Pity you disappointed me. The fact that I have a working SSL HTTP server written from scratch would imply that I know exactly what it is... wouldn't it? Not that reality ever is a playing factor with you.

              Sure I am. You just keep telling yourself that. If you refuse to state the format and algorithm, you are just being a cowar
              • Actually I was expecting you to just be a retard again

                So ... your stupidity was part of a clever plot again. Read up on the SSL spec, and you'll have some hope of understanding how it works.

                "which type SSL is?". ROTFLMAO. I'm happy to see my initial assessment of your capability confirmed in full.

                The fact that I have a working SSL HTTP server written from scratch would imply that I know exactly what it is... wouldn't it?

                Is that supposed to be impressive? Anyway, you've just used an API ... just like
                • "which type SSL is?". ROTFLMAO. I'm happy to see my initial assessment of your capability confirmed in full.

                  Except I said: "Oh, and I'm sure that you can tell me which type SSL is? Go right ahead, I'm dying to hear it..." Anybody with any level of literacy past that of a 12 year old would have been able to establish my meaning. I'm glad you still didn't fail to prove your aren't retarded. The only way I could have made my intentions more obvious were to have a neon sign, which you still wouldn't get.
                  • Anybody with any level of literacy past that of a 12 year old would have been able to establish my meaning

                    Right. More backpedalling. Whatever. It's clear that you don't know the first thing about it.

                    Using only SHA1 hash chaining

                    That's not what you said originally. And you maintained this for two or three posts.

                    Anyway, you ran the key through SHA1, and xored it with your ASCII clear text, and it produced ASCII text? You ought to learn some maths, in order not to make a fool of yourself.

                    Uhm, in relat
                    • Ah, another "challenge" from Oregon. It quite well documented. And, of course, the proper way is going to depend on what you actually want to do. I'm amazed that you found this difficult, for such an self-professed genius.
                      Then you will have no problem cutting and pasting it, or establishing conditions for it, right?

                      Anyway, you ran the key through SHA1, and xored it with your ASCII clear text, and it produced ASCII text? You ought to learn some maths, in order not to make a fool of yourself.
                      Nope, try a
                    • Then you will have no problem cutting and pasting it, or establishing conditions for it, right?

                      You're talking about blocking or non-blocking IO? I think it's clear, again, that you don't have a clue what you are talking about, and need to be treated as one would a recalcitrant child.

                      Nope, try again Mr. Dipshit

                      Well, that's what's described in Applied Cryptography, is what everyone refers to by this, and is what the Perl module is (roughly) doing, with the addition of a random value.

                      It's quite clear yo
                    • An insult from someone who had to move to Oregon, of all places, to find work, and who demonstrates a continual ignorance of technical issues in his posting shouldn't go around insulting people.

                      I moved to Oregon in the months of it's highest unemployement. I still get job offers down in California. I was employed after moving here for 2 months. I've proven myself capable, yet you haven't.

                      This really is great though, I don't have any self-esteem issues like you possess to try to defend. I know what I
                    • I moved to Oregon in the months of it's highest unemployement. I still get job offers down in California.

                      Whatever. For what? "sysadmin"? "web developer"? PHP programmer?

                      I was employed after moving here for 2 months. I've proven myself capable, yet you haven't

                      You mean like not understanding the OpenSSL API from the perfectly clear POD documentation? I wouldn't have called that "capable" exactly. Or how about your confusion over the encryption used in SSL?

                      Anyway, you haven't, except in your mind. You'v
                    • You mean like not understanding the OpenSSL API from the perfectly clear POD documentation? I wouldn't have called that "capable" exactly. Or how about your confusion over the encryption used in SSL?

                      You are funny. I know lots of people with lots of OpenSSL experience who are saying the OpenSSL documentation is shit. In fact, on most of the posts I've read on the subject, they say the test code is the best documentation -- they're right. That was what I used. It works now, so you seem to be flawed in y

Slashdot Top Deals

The next person to mention spaghetti stacks to me is going to have his head knocked off. -- Bill Conrad

Close