Hi, if you are documenting this data anywhere that is publicly accessible, I would be very interested — I am a Comp Sci doctoral candidate specializing in Information Security & Privacy and could use this data toward my research. Can DM/email if you need more details.
-
-
-
Of course! Can you send me an email? Twitter name at http://github.com .
Kraj razgovora
Novi razgovor -
-
- Još 1 odgovor
Novi razgovor -
-
See https://freedom-to-tinker.com/blog/felten/the-linux-backdoor-attempt-of-2003/ … for story by
@EdFelten of a pre-git commit to the Linux kernel.Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I don't know of any specific examples, but in JS, using Object.assign is a seemingly harmless way to enable prototype pollution vulnerabilities into unsuspecting projects. I'd look there.
-
Huh, never heard of that. Can you share an example of how it works?
- Još 2 druga odgovora
Novi razgovor -
-
-
Thank you for the new display name.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
most npm packages
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Is this problem solvable? Say I create a new GitHub account and submit a PR with a bug, accidentally. And say I create a new GitHub account and submit a PR with a bug, intentionally. How can anyone besides me know whether a PR matches #1 or #2?
-
Because they should have a lot more information than just that it's a new account. Cross referencing ip (was the account generated behind a vpn?) and various other "higher risk" factors about the given account would make it easier for maintainers to know when to be careful
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.