Whaaaaaaaaat. You should seriously submit this to dailywtf.com. This has been around 10 more WTFs than I was planning on today. :)
Ryan
· 1 year ago
I am afraid this is where we have gotten ourselves. Software is so easy now that the 80%ers and mediocrity are ever present. I miss the days of custom software, it took longer, but stuff worked. I have to combine many open source 'frameworks' in my job these days and .... *shotgun blast*
John Lollen
· 1 year ago
Don't even pretend you know how to code Ruby fan boy.
Really - stick with your Dreamweaver and your hopes you will pay off the debt from your Arts degree when your next "big break".
Michael Campbell
· 1 year ago
@John,
wow, someone needs a hug.
macournoyer
· 1 year ago
*hugs john*
it's gonna be ok john, we love you
Bosko
· 1 year ago
I think I know which API you're talking about. :-)
Bosko
· 1 year ago
btw, I tried to write a ruby lib to wrap the particular API you're talking about (if it's the same one I'm thinking) some time ago - I started it and gave up after a while (perhaps that's what you're looking at?) Back then there was a single encryption scheme, blowfish with ECB block cipher (and a non-obvious padding scheme - nul bytes :-( - non-obvious because one wouldn't think a nul-byte scheme would be used since it only works for non-binary data). ECB sucks. I was told that https was "too slow".
I spent some time in person speaking to the developer there, nice guy and all, but I walked away from that admittedly pretty spirit deprived.
Coincidentally we're trying to revive the lib here now, but are hitting problems with the crypto bits again -- I think something was inadvertently tweaked again on their end.
Anyway, if we're talking about the same lib, I believe they've got a way to enable "https mode" so that you can avoid the whole blowfish + ECB/CBC/whatever symmetric mess.
All Comments
Really - stick with your Dreamweaver and your hopes you will pay off the debt from your Arts degree when your next "big break".
wow, someone needs a hug.
it's gonna be ok john, we love you
I spent some time in person speaking to the developer there, nice guy and all, but I walked away from that admittedly pretty spirit deprived.
Coincidentally we're trying to revive the lib here now, but are hitting problems with the crypto bits again -- I think something was inadvertently tweaked again on their end.
Anyway, if we're talking about the same lib, I believe they've got a way to enable "https mode" so that you can avoid the whole blowfish + ECB/CBC/whatever symmetric mess.