Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License Inquiry for Code Usage #4

Open
Andrei-Fogoros opened this issue Mar 7, 2025 · 1 comment
Open

License Inquiry for Code Usage #4

Andrei-Fogoros opened this issue Mar 7, 2025 · 1 comment

Comments

@Andrei-Fogoros
Copy link

Andrei-Fogoros commented Mar 7, 2025

Hello @ia

I am using a code snippet from the following file in this repository: https://github.com/ia/connect/blob/master/samples/winsock/getadaptersaddresses.c

I would like to know which license applies to this file and what the repository's overall license is.

Thank you! :)

@ia
Copy link
Owner

ia commented Mar 10, 2025

Hello, @Andrei-Fogoros.

First of all, thank you for the interest to my old little experimental project and collection of snippets.

Second, this is a good question.

Third, as stated somewhere in README (I hope), connect is more like RnD project than the production ready library, so while I was working on it, I was grabbing any snippets and samples I could find in public domain or in any other FOSS projects. Therefore, as of for that exact file, you can do with that whatever you want. It was long time ago, and since there is no any mention, it can be considered as public domain. But I AM NOT A LAYWER and this is NOT A LEGAL ADVICE. If you work on some hobby project, then I don't think you should worry about anything, and if it's some corporate code, then you just probably should talk to your legal department, but I guess it really can be considered as public domain . I think I picked it from some parts of WINE and/or from ReactOS, when I was trying to understand how exactly ipconfig works in Windows and where & how ipconfig gets the information about network interfaces and their properties.

Fourth, I have in my ToDo list to go trhough every repo and to make sure that there is licensing policy because it's really well recommended indeed for exactly such cases as you addressed.

Fifth, pardon for late reply.

I hope it helps. Good luck with your project. Happy Hacking! ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants