News for hackers. Stuff that matters.
Re:GitHub Copi­lot inves­ti­ga­tion by randomdata on Tuesday October 18, 2022 @12:34AM (#33243019)
> So you were probably illegally accessing another person or companies systems.

Illegal would imply some kind of intent or malice. I was legitimately trying to access the executed result, which I would have been authorized to do if the service was operating normally.

> What you should've done was notify the owners of the incorrectly configured system and left it at that.

Seems unrealistic to "leave it at that". I had to read the output to understand it wasn't what I expected, and once I read it I knew how to code, at least to a cursory degree. The code was simple and it was a service I used frequently, so it was immediately clear how the code translated to the results I was accustomed to.

> I use Github like a bank, not a public library (unless I'm working on open source). I never would've allowed them to read through all my code and use it for profits without at least asking.

I don't know what kind of banks you deal with, but banks normally do read through your banking records and use that information to sell services to their clients – notably loans, which require knowledge of your deposits to offer.

There are no comments on this comment yet.