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

Is this repository abandoned? #166

Open
IlyaChizhanov opened this issue Mar 18, 2024 · 8 comments
Open

Is this repository abandoned? #166

IlyaChizhanov opened this issue Mar 18, 2024 · 8 comments

Comments

@IlyaChizhanov
Copy link

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.

@Mouwrice
Copy link

Mouwrice commented Apr 1, 2024

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.

@robvdl
Copy link

robvdl commented Jun 19, 2024

No this is likely a takeover attempt, don't do it. From Moscow, watch it!

@robvdl
Copy link

robvdl commented Jun 19, 2024

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.

@robvdl
Copy link

robvdl commented Jun 19, 2024

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.

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.

@Kreijstal
Copy link

No this is likely a takeover attempt, don't do it. From Moscow, watch it!

but t

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.

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.

someone makes a fork

takover

moving organization and giving someone power or admin rights

ain't that takeover too lol? in a wway

@IlyaChizhanov
Copy link
Author

IlyaChizhanov commented Jun 26, 2024

No this is likely a takeover attempt, don't do it. From Moscow, watch it!

Oh my God. I was exposed. You are so insightful. You did a great job of exposing me 😆

@adminy
Copy link

adminy commented Jul 8, 2024

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.

@robvdl
Copy link

robvdl commented Jul 9, 2024

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.

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

5 participants