-
### 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…
-
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…
-
#### Brief summary of issue / Description of requested feature:
Several players have reported that the "TLS connection" option was enabled by default for them when connecting to a predefined game:
…
vadi2 updated
1 month ago
-
### 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…
-
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?
-
## In what area(s)?
/area API
## Describe the feature
As per configmap comment:
https://github.com/knative/serving/blob/c91f8c43eb806fea4f6315d970f6d78e89a96d7c/config/core/configmaps/feat…
nak3 updated
3 months ago
-
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.
-
### Description
Whenever we mention that a particular parameter value should be set/enabled "for security reasons" we should probably mention in the description which rules we are following or whic…
-
The library should provide more functionality out of the box, trying hard to ensure that library users get a secure oauth handshake by default.