Viewing profile — shartte
shartte
HN member- Joined
- Thu, Apr 29, 2021, 8:48 PM UTC
- HN karma
- 40
- Public activity
- 9 items
- HN profile
- View on Hacker News ↗
About shartte
No profile information was provided.
Recent public activity
-
comment
Comment #37254442
Hashes of known good drivers should be whitelisted explicitly if they are known to have been signed correctly before revocation. Direct trust should trump a PKI here.
-
comment
Comment #35391501
> Security bugs aren't really an issue because you are just using the Steam app to navigate 1 site, Valve's. You only see what Valve presents. I don't think you want to explain tha…
-
comment
Comment #31193082
It looks interesting, but seems to be dead. The repository has virtually no activity since september 2020.
-
comment
Comment #30999958
I think the parent poster meant that if X.509 Name Constraints were widely deployed, Visas CA could be limited to Visa's TLD+1s. In the same way, government affiliated CAs could be…
-
comment
Comment #29675903
If they are using GMail for work, the DNS just points to GMails actual server and authenticates using DKIM as well. Google for Work will provide you with the necessary DNS entries …
-
comment
Comment #29544383
I believe this is the default in Spring Boot. Logback is used by their starters (see https://docs.spring.io/spring-boot/docs/current/reference/ht... ).
-
comment
Comment #29544127
You can disregard a combination of log4j-api+log4j-over-slf4j (as is used by default by Spring Boot) since the actual vulnerability is not in the Log4j2 API, but rather in the actu…
-
comment
Comment #26987484
The sole reason really is that the contents of a HttpOnly cookie cannot be exfiltrated by an XSS-exploit, while a JWT stored in localStorage could be. This would probably only make…
-
comment
Comment #26986544
> It is good practice to always use the SameSite directive with cookies as this provides protection against CSRF attacks. Be careful with assuming SameSite fully protects from CSRF…