To those wanting to use HTTP and/or HTTPS

[LexiBigCheese]

You'll want to comment out the assertion that causes issue #174 to have a panic, then cargo clean so cargo rebuilds std with this change.
Then, patch the ring crate to be the one I'm trying to get pulled into the main branch,
EDIT: It has been pulled!
EDIT2: Note: Point at ring's main branch.

[patch.crates-io]
ring = {git = "https://github.com/briansmith/ring"}

and ensure

[profile.dev.package.ring]
opt-level = 1
[profile.release.package.ring]
opt-level = 1

Note that patch and profile sections go in Cargo.toml, if you're using a cargo workspace, it does in the workspace's Cargo.toml
Additionally, you'll want the environment variable

export CFLAGS_armv6k_nintendo_3ds="-march=armv6k -mfloat-abi=hard -finline-limit=100000"

And now, the minreq crate will now let you do https.
Having a timeout may be that which causes the ureq crate to fail, I've been told to look into yielding when listening on an mpsc::Receiver, but I'm not that great at modifying std, so instead I just modified and patched ehttp to use minreq on cfg(target_os = "horizon")

[lrk]

Hi @LexiBigCheese,

i tried your configuration, trying to get ssl to work with tungstenite (cf #207), but i get compilation errors on ring crate:

Compiling ring v0.17.8 (https://github.com/briansmith/ring?rev=4955dd7ad9a0b5a5d4426b588d20cd7549205958#4955dd7a)
warning: ring@0.17.8: In file included from /Users/lrk/.cargo/git/checkouts/ring-794206c1dca33632/4955dd7/crypto/curve25519/curve25519.c:24:
warning: ring@0.17.8: In file included from /Users/lrk/.cargo/git/checkouts/ring-794206c1dca33632/4955dd7/crypto/curve25519/internal.h:20:
warning: ring@0.17.8: In file included from /Users/lrk/.cargo/git/checkouts/ring-794206c1dca33632/4955dd7/crypto/curve25519/../internal.h:115:
warning: ring@0.17.8: /Users/lrk/.cargo/git/checkouts/ring-794206c1dca33632/4955dd7/include/ring-core/check.h:27:11: fatal error: 'assert.h' file not found
warning: ring@0.17.8: # include <assert.h>
warning: ring@0.17.8:           ^~~~~~~~~~
warning: ring@0.17.8: 1 error generated.
error: failed to run custom build command for `ring v0.17.8 (https://github.com/briansmith/ring?rev=4955dd7ad9a0b5a5d4426b588d20cd7549205958#4955dd7a)`

same error with ring main branch or your PR commit.

I'm on Macos Monterey, and got error that CFLAG -finline-limit was not supported (so i removed it)

My cargo file:

... 

[dependencies]

ctru-sys = { git = "https://github.com/rust3ds/ctru-rs.git" }

ctru-rs = { git = "https://github.com/rust3ds/ctru-rs.git", features = [
  "romfs",
] }

citro3d = { git = "https://github.com/rust3ds/citro3d-rs.git" }
serde = { version = "1.0.217", default-features = false, features = [
  "derive",
  "alloc",
] }

serde_json = { version = "1.0.138", default-features = false, features = [
  "alloc",
] }
crossbeam-channel = "0.5.14"
url = "2.5.4"
lazy_static = "1.5.0"

tungstenite = { version = "*", features = ["rustls-tls-webpki-roots"] }
rustls = { version = "0.23.23", default-features = false, features = [
  "std",
  "tls12",
  "ring",
] }

# https://github.com/rust3ds/ctru-rs/issues/205
[patch.crates-io]
ring = { git = "https://github.com/briansmith/ring", rev = "4955dd7ad9a0b5a5d4426b588d20cd7549205958" }
[profile.dev.package.ring]
opt-level = 1
[profile.release.package.ring]
opt-level = 1

Any idea why it fail to build and how to solve that ?

[LexiBigCheese]

best thing you can try to do is look for the header file and look for where the flags for the compile of the file that needs to be compiled is and point one at the other. i have no clue where you'd even look for that (i figured out how to get HTTPS on the 3DS like... almost a year ago today i just made the commits in recent times so i can't remember what problems exactly i ran into >.<)

if all else fails, try a linux docker container.

[iamcco]

@lrk About the ring you can take a look at my fork, I don't know if it's the best solution, but it works. https://github.com/save-cloud/ring/tree/v0.17.10-3ds

[DCNick3]

Another approach might be using rustls-rustcrypto for the crypto backend. It's pure rust, so this circumvents most compat problems

[ian-h-chamberlain]

Thanks for raising this, your research and efforts here seem like great information for people looking to use this stuff!

However, it doesn't sound like there's anything actionable (bug or feature) for this repo, so I'm going to go ahead and move it to a discussion. Please feel free to continue posting useful info there!

See also https://github.com/orgs/rust3ds/discussions/199