-
Notifications
You must be signed in to change notification settings - Fork 129
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
Is this repository abandoned? #166
Comments
I am getting the same feeling here. Seems like there has been no activity for over 8 months now. Maybe someone should fork the repository and continue there. Things are getting outdated. |
No this is likely a takeover attempt, don't do it. From Moscow, watch it! |
It might not be, but then it might be a takeover attempt, think the XZ backdoor. Exactly the same kind of messages. I don't trust it. |
The issue is that this repository is under an individual rather than a group, or organisation whatever GitHub calls it. But archiving the repo isn't the answer because then the Russian fork will likely get promoted and a backdoor inserted soon after. You really don't want that. Moving it to an group/organisation and having multiple people able to merge is the answer. |
but t
takover
ain't that takeover too lol? in a wway |
Oh my God. I was exposed. You are so insightful. You did a great job of exposing me 😆 |
Since this "sso" component of openconnect is just to handle browser auth, there is not much that it does. I'm thinking if its possible to strip away all the unnecessary code and put the "parsing xml" bit into a python package, then make it as an optional dependency into the original openconnect project. |
We actually had a client recently switch to Microsoft SSO for their GlobalConnect firewall and couldn't get in anymore. I tried a bunch of solutions including this one and I just couldn't get it to work sadly. I wish I could have kept debugging it so I could have raised a meanigful ticket, but client wants to move on. |
Is this repository abandoned?
There are a few GitHub issues open and many PRs waiting to be merged.
If it is abandoned, then I suggest updating the README and archiving the repository for future readers' reference.
The text was updated successfully, but these errors were encountered: