-
### Description of the feature you would like to add
I can't speak for other providers, our main concern might be OpenStack specific and as that's also the only infra I'm familiar with, I'll talk abo…
-
using the Ruby on Rails Framework options
-
### Pitch
It has been almost 5 years since authorized fetch was first introduced to the fediverse (late 2018). It seems like it would be reasonable to reevaluate enabling it by default at this point…
-
Clusters in default configurations shall be secure by default.
At this point we open a lot of insecure ports that we should not start by default and use the secure variants instead. There are multipl…
-
### The problem
I try to send unsecured mqtt message to my broker, but receive esp-idf errors caused tls connection fails.
Why tls error occured for insecure publish? `[E][mqtt.idf:162]: Last er…
-
Every ScyllaDB cluster should be secure by default. We already have CQL over TLS and automatic certificates for it so it starts by default. With that ready, and when it is promoted from beta to GA, we…
-
Is there any way we can get a `https://` in the URL builds without having to specify the `Secure()` function each time? Is there still a requirement for `http://` only out there?
-
Why not make 'secure' be the default? It seems like the web is heading towards a secure-by-default design with HTTP/2 being based on SSL.
-
The library should provide more functionality out of the box, trying hard to ensure that library users get a secure oauth handshake by default.
-
- Update all start-up scripts or start guide docs with TLS or auth.
- Never allow unauthenticated client access by default (either by auth or TLS)?
- Enable TLS by default for peer-to-peer connectio…
gyuho updated
2 years ago