Viewing profile — securesaml
securesaml
HN member- Joined
- Thu, Sep 19, 2024, 5:50 PM UTC
- HN karma
- 69
- Public activity
- 25 items
- HN profile
- View on Hacker News ↗
About securesaml
No profile information was provided.
Recent public activity
-
comment
Comment #48127860
Nice find. The tokens being leaked in actions log was not one of the security implications I thought of when they released the feature. How many other actions/libraries do you thin…
-
comment
Comment #48127798
It's limited to ghs_ (server to server token's), that have the new format enabled: https://github.blog/changelog/2026-04-24-notice-about-upcomi... (and actions that use the vulnera…
-
comment
Comment #47940951
Github enterprise cloud is on github.com and with more features: http://github.com/account/enterprises/new They don't host github enterprise server for you (though gitlab has somet…
-
comment
Comment #46627367
there's still some risk of publishing an attacker's key. For example, what if the attacker's key had access to sensitive user data?
-
comment
Comment #46625950
it is less of a problem for revoking attacker's keys (but maybe it has access to victim's contents?). agreed it shouldn't be used to revoke non-malicious/your own keys
-
comment
Comment #46624660
I wouldn’t recommend this. What if GitHub’s token scanning service went down. Ideally GitHub should expose an universal token revocation endpoint. Alternatively do this in a privat…
-
comment
Comment #46622141
I'm not too sure about the root cause about tj-actions. IIRC there are some libraries that compromised by actions injections vulnerabilities, where a security specialist could have…
-
comment
Comment #46621455
I have seen small utility libraries like tj-actions get compromised because there aren't any security specialists looking at the library. My main concern is supply chain compromise…
-
comment
Comment #46619875
The problem is lots of open source is unmaintained/insecure, and there aren't any security engineers on those open source libraries. For the library to be secure, there needs to be…
-
comment
Comment #46619699
Correct, maintainers can say that and get shamed. And it leads to unmaintained libraries, since companies don't want to pay. At some point, is open sourcing your work a liability?
-
comment
Comment #46618785
The problem is more so maintenance. The expectation of FOSS is that the users and maintainer work together to resolve bug fixes/features/security issues. However many companies wil…
-
comment
Comment #45066640
Google has a program where you can submit patches to OSS projects (including libxslt) https://bughunters.google.com/about/rules/open-source/492808... The patches need to fix a syst…
-
comment
Comment #44899918
I agree MSFT should have paid way more. My point is if that FFmpeg, tried to raise more awareness of the issue, say talk to news outlets, they could get much more funding from MSFT…
-
comment
Comment #44899865
It's usually the more user-facing products that can thrive on this freemium model (probably full web apps or a lot of code). For example, laravel might get a lot of funding from th…
-
comment
Comment #44899720
https://news.ycombinator.com/item?id=39912916 they did get some funding after asking.
-
comment
Comment #44899170
> Companies say "This my code when I need it, and it's your code when it breaks", and developers read the fine print very late, because they thought exposure is valuable. I think t…
-
comment
Comment #44898519
I agree that open source infrastructure needs to be funded. I think first there needs to be a mindset shift in who's responsible for open source. Currently when new vulnerabilities…
-
comment
Comment #44898450
sure. But companies believe that open source developers owe everything to the them (i.e. fixing bugs, contributing to feature requests, critical security releases ...).
-
comment
Comment #44856425
For me, I don't think that the application is public exposed is really the problem (i.e. not in intranet). I think the real problem is that these applications (Entra ID) are multi-…
-
comment
Comment #44803782
I am working on an SAML Attacker (that basically tests web apps against all known SAML exploits). It includes all the test cases. I can share you the repository if you want to inte…
-
comment
Comment #44339461
Issue is not with go's parser, but instead about processing layer using different input than verifying layer [1] We patched the gosaml2 (and other go saml libraries), by ensuring o…
-
comment
Comment #44338326
The correct conclusion is: https://news.ycombinator.com/item?id=44337330 The problem of trying to ensure that each parser behaves the same for all input is twofold: - JSON and XML …
-
comment
Comment #44337979
See: https://bsky.app/profile/filippo.abyssdomain.expert/post/3le... that was about a signature wrapping attack in crypto, but it also applies here.
-
comment
Comment #44337964
This is correct. In blog post they say: > Other examples exist, but most follow the same pattern: the component that does security checks and the component that performs the action…
-
comment
Comment #43376552
[dead]