cryptoBYOND

Page: 1 2
ID:1622743
 
Jul 9 2014, 3:04 am (Edited on Jul 9 2014, 4:24 pm)
Keywords: 1, 224, 256, 384, 512, byond, crypto, cryptopp, hashing, sha
Library URL: Download cryptoBYOND

Available Functions:

SHA1();
SHA224();
SHA256();
SHA384();
SHA512();


How to use:

mob/verb/Test(T as text)
   src<<SHA1(T);
   src<<SHA224(T);
   src<<SHA256(T);
   src<<SHA384(T);
   src<<SHA512(T);


Enjoy!

Please feel free to send me a generous donation below
Jul 9 2014, 2:05 pm
Great library! I'll probably use this in the future over BYOND's built-in MD5 function.
Thanks much!
Jul 9 2014, 2:31 pm
No problem. If you happen to come across any other hashing algorithm's that you would like to see in BYOND, I'll be more than happy to build it into this library.
Jul 11 2014, 12:03 am
This is exactly what we all needed. Thank you.
Jul 11 2014, 12:35 am
You're welcome :)
Jul 11 2014, 11:02 pm
Provide source so that linux libs can be built please.
Jul 11 2014, 11:04 pm (Edited on Jul 12 2014, 12:59 am)
Ssj4justdale

Actually, after downloading you've not included your code files. It's just a .dme

Jul 12 2014, 11:58 am
the crap, o.o I dunno what happened but I'll fix it now.
Jul 12 2014, 12:05 pm
I'll dual-boot my laptop and create a linux library, I'm busy at the moment attending other matters.
Jul 12 2014, 12:07 pm
In response to Zecronious
Zecronious wrote:
Ssj4justdale

Actually, after downloading you've not included your code files. It's just a .dme

It was something with the compiler/packager not including the included files. I don't know what occurred but after fooling around for a bit, I got it to fix.

Jul 12 2014, 12:38 pm
In response to Ssj4justdale
Seeming as you're implementing known cryptography hashing functions, is there any harm in open sourcing?
Compiling for specific architectures allows certain speed improvements to be made.
Jul 12 2014, 12:46 pm
no harm whatsoever, just on my phone at the moment. What I meant to say is that i'll release the source after I build the linux library
Jul 12 2014, 12:49 pm
In response to Ssj4justdale
Oh okay, cool!
Jul 24 2014, 4:58 pm
In response to Ssj4justdale
Ssj4justdale wrote:
no harm whatsoever, just on my phone at the moment. What I meant to say is that i'll release the source after I build the linux library

How's this coming along?
Jul 24 2014, 4:59 pm
It's on my Linux VPS, I'll upload when I get home
Apr 30 2015, 6:20 pm
And now?
May 10 2015, 2:10 am
What's wrong with md5 for BYOND's purposes?
May 10 2015, 8:50 am
In response to Toadfish
Md5 has been proven time and time again to be completely insecure. It has hash collision issues (meaning sometimes there's two things that have the same hash) and has already been cracked. Meaning, even if you salt your hashes chances are someone can turn your md5 hash into plaintext anyway.

More info: https://crackstation.net/hashing-security.htm
Jun 12 2015, 8:31 pm
Heres the source / works on linux when compiled and libs installed.

#include <string>
#include "cryptopp/sha.h"
#include "cryptopp/base64.h"
#include "cryptopp/hex.h"

#ifdef WIN32
extern "C" __declspec(dllexport) const char * SHA1(int argc, char ** argv);
extern "C" __declspec(dllexport) const char * SHA224(int argc, char ** argv);
extern "C" __declspec(dllexport) const char * SHA256(int argc, char ** argv);
extern "C" __declspec(dllexport) const char * SHA384(int argc, char ** argv);
extern "C" __declspec(dllexport) const char * SHA512(int argc, char ** argv);
#else
#include <cstring>
extern "C" const char * SHA1(int argc, char ** argv);
extern "C" const char * SHA224(int argc, char ** argv);
extern "C" const char * SHA256(int argc, char ** argv);
extern "C" const char * SHA384(int argc, char ** argv);
extern "C" const char * SHA512(int argc, char ** argv);
#endif

using namespace std;
string output;

const char * SHA1(int argc, char ** argv)
{
    CryptoPP::SHA1 hash;
    byte digest[ CryptoPP::SHA256::DIGESTSIZE ];
    hash.CalculateDigest( digest, (const byte *)argv[0], strlen(argv[0]) );

    CryptoPP::HexEncoder encoder;
    output = "";
    encoder.Attach( new CryptoPP::StringSink( output ) );
    encoder.Put( digest, sizeof(digest) );
    encoder.MessageEnd();

    return (const char *)output.c_str();
}


const char * SHA224(int argc, char ** argv)
{
    CryptoPP::SHA224 hash;
    byte digest[ CryptoPP::SHA224::DIGESTSIZE ];
    hash.CalculateDigest( digest, (const byte *)argv[0], strlen(argv[0]) );

    CryptoPP::HexEncoder encoder;
    output = "";
    encoder.Attach( new CryptoPP::StringSink( output ) );
    encoder.Put( digest, sizeof(digest) );
    encoder.MessageEnd();

    return (const char *)output.c_str();
}

const char * SHA256(int argc, char ** argv)
{
    CryptoPP::SHA256 hash;
    byte digest[ CryptoPP::SHA256::DIGESTSIZE ];
    hash.CalculateDigest( digest, (const byte *)argv[0], strlen(argv[0]) );

    CryptoPP::HexEncoder encoder;
    output = "";
    encoder.Attach( new CryptoPP::StringSink( output ) );
    encoder.Put( digest, sizeof(digest) );
    encoder.MessageEnd();

    return (const char *)output.c_str();
}


const char * SHA384(int argc, char ** argv)
{
    CryptoPP::SHA384 hash;
    byte digest[ CryptoPP::SHA384::DIGESTSIZE ];
    hash.CalculateDigest( digest, (const byte *)argv[0], strlen(argv[0]) );

    CryptoPP::HexEncoder encoder;
    output = "";
    encoder.Attach( new CryptoPP::StringSink( output ) );
    encoder.Put( digest, sizeof(digest) );
    encoder.MessageEnd();

    return (const char *)output.c_str();
}

const char * SHA512(int argc, char ** argv)
{
    CryptoPP::SHA512 hash;
    byte digest[ CryptoPP::SHA512::DIGESTSIZE ];
    hash.CalculateDigest( digest, (const byte *)argv[0], strlen(argv[0]) );

    CryptoPP::HexEncoder encoder;
    output = "";
    encoder.Attach( new CryptoPP::StringSink( output ) );
    encoder.Put( digest, sizeof(digest) );
    encoder.MessageEnd();

    return (const char *)output.c_str();
}
Jun 26 2015, 2:20 pm
In response to Doohl
Doohl wrote:
Md5 has been proven time and time again to be completely insecure. It has hash collision issues (meaning sometimes there's two things that have the same hash) and has already been cracked. Meaning, even if you salt your hashes chances are someone can turn your md5 hash into plaintext anyway.

More info: https://crackstation.net/hashing-security.htm

So what? Nobody is going to do a cryptographic attack on a BYOND game.

Also, chosen prefix attacks on MD5 are still crappy so there is no reasonable way to use its vulnerabilities in a practical BYOND setting.
Page: 1 2