mirror of
https://github.com/Clipy/Clipy.git
synced 2026-04-26 01:25:58 +03:00
[GH-ISSUE #118] unsolicited HTTPS connections to amazonaws.com #66
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Clipy#66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vollkommenheit on GitHub (Nov 3, 2016).
Original GitHub issue: https://github.com/Clipy/Clipy/issues/118
Originally assigned to: @Econa77 on GitHub.
Why is Clipy opening HTTPS connections, seemingly almost every minute, to either of the following addresses, even though "automatically check for update" is disabled?
ec2-54-235-114-192.compute-1.amazonaws.com
ec2-23-23-110-243.compute-1.amazonaws.com
I also see HTTPS connections to 104.27.179.207 and ec2-23-23-110-243.compute-1.amazonaws.com, when a check update is manually requested.
I did a cursory search (with grep) for those addresses in all the files of the Clipy source code, without turning anything up. Where are those addresses specified?
@Econa77 commented on GitHub (Nov 4, 2016):
@vollkommenheit Clipy is using fabric to collect crash and error log.
Those aws addresses is connect fabric services.
For example.
However, I'm sorry to have arbitrarily collected logs. Next Clipy release, we add collect log option at preference window. Clipy release binaries is no change open source code.
Thank you reporting issue, and using Clipy.
@vollkommenheit commented on GitHub (Nov 4, 2016):
Thanks for clarifying.