This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-15
Channels
- # aleph (5)
- # announcements (1)
- # architecture (35)
- # babashka (9)
- # beginners (87)
- # chlorine-clover (13)
- # cider (3)
- # cljdoc (12)
- # clojure (16)
- # clojure-australia (2)
- # clojure-dev (4)
- # clojure-europe (5)
- # clojuredesign-podcast (21)
- # clojurescript (19)
- # conjure (1)
- # core-async (1)
- # data-science (1)
- # emacs (44)
- # events (2)
- # helix (1)
- # leiningen (2)
- # malli (31)
- # pathom (3)
- # pedestal (31)
- # portal (3)
- # reagent (20)
- # reitit (5)
- # reveal (2)
- # rewrite-clj (18)
- # tools-deps (6)
- # xtdb (5)
Hello! I’m trying to “hand-craft” a signed AWS HTTP request following these instructions
https://docs.aws.amazon.com/general/latest/gr/sigv4_signing.html
One blocker that I’m hitting is the HMAC SHA256: looks like it’s possible via java.crypto
, which isn’t part of bb
I do also see that https://funcool.github.io/buddy-core/latest/02-mac.html supports it as well (presumably via java.crypto)
I just had the idea to shell out to openssl
directly, which seems like a super reasonable approach for my tinkering needs
$ echo -n "value" | openssl sha256 -hmac "key"
I think we could maybe have a pod around buddy / security (provided this is only data in / data out)
I’m happy with shelling out :thumbsup:
up to you (of course) if/when to try incorporating `java.security` java.crypto
🙂 I trust you
It already has some java.security classes (for calculating SHA-256), just not java.crypto
yes, sorry, that’s what I meant