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

Force IPv4 for every curl call made to lastpass API servers #488

Merged
merged 1 commit into from
Mar 20, 2019

Conversation

waterkip
Copy link
Contributor

Users with IPv6 enabled report slowness due to IPv6. The default of Curl
is to look at both IPv6 and IPv4. This quickfix makes it possible for
users to not experience these issues. We may need to do this differently
by enabling lpass -4 to force IPv4 and -6 for v6.

Fixes: #440, #475
Signed-off-by: Wesley Schwengle wesley@schwengle.net

Users with IPv6 enabled report slowness due to IPv6. The default of Curl
is to look at both IPv6 and IPv4. This quickfix makes it possible for
users to not experience these issues. We may need to do this differently
by enabling lpass -4 to force IPv4 and -6 for v6.

Fixes: lastpass#440, lastpass#475
Signed-off-by: Wesley Schwengle <wesley@schwengle.net>
@GPaulovics
Copy link
Contributor

After a little digging and talking with DevOPS it is totally possible that lastpass.com will not work with IPv6. So until it is confirmed that its fixed I'll merge this, and once we introduce IPv6 we can think about how to handle both IPv4 and IPv6.

Thank You @waterkip

@GPaulovics GPaulovics merged commit 5531e25 into lastpass:master Mar 20, 2019
@waterkip waterkip deleted the gh-440-quickfix branch March 26, 2019 10:29
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

Successfully merging this pull request may close these issues.

force ipv4 function
2 participants