cross-posted to: reddit r/selfhosted
Kinda proud of this, so forgive me while I brag. I found a likely “phone home” tracking image in DocuSeal. I searched around: there was an extant issue about the image. I asked the devs: would they accept a PR to remove the image? A maintainer responded quickly that they were not interested in a PR to remove it, so I forked it in minutes with my tiny hack, built a new Docker image and re-deployed to my server after making a one-line change in a Docker Compose file.
Here’s the hack: github.com/meonkeys/docuseal/commit/e710678d
Happy to share my compose config as well if folks are interested.
I do want to put in a plug for DocuSeal: they made an excellent thing. It’s a fast and beautiful app for adding signatures to PDFs, similar to DocuSign or HelloSign, but awesomely AGPL licensed and easy to self-host. I got it running in minutes and it worked very well. I support what they’re doing and I want to see them succeed. OpenSign looks cool too but I haven’t tried that one yet.
So yeah. Self-hosting and FOSS FTW!
just_another_person@lemmy.world 4 months ago
Okay, well they were very clear about it, and they have a pro version, so aren’t removing the customizations that exist.
Secondly, that isn’t a “phone home” bit that you hacked around, it’s literally a header that loads a GitHub badge, and that’s it. It’s part of a lot of open source projects.
Blocking the DNS of the GitHub host it’s calling back to is sufficient enough for everyone if this is a concern (it’s of no security concern, freal), and you don’t need a fork for this to be fixed. Maintaining a fork is an insane amount of work, and trusting someone who is maintaining a forked repo is WAYYYYYY more risky than just using the official repo, which has thousands of stars, and multitudes of users poking through it’s code.
I for one would never touch your forked repo without doing a full diff, and I’m not going to worry about doing that every time a release is missed by you, or a fix isn’t upstreamed…yada yada. I would just the official repo, and block the offending GitHub domain if I found it offensive, which I don’t.
Know what I mean?
meonkeys@lemmy.world 4 months ago
are you sure? I’m not. In truth, only they know. Here’s the code I worked around in my fork. Why does it fetch an external image? They could just include it in the repo. Why is it fetched from
docuseal.co
? I would guess GitHub renders badges like this too.Sure, but why not default to privacy in the upstream source? Why make users and self-hosters do extra work? Feels more like a penalty for non-Enterprise users than a benefit for paying up: you’ll either pay with money or your data.
Also note: it is actually
docuseal.co
that would be blocked (I incorrectly guessed it pulled the image directly from GitHub), so that’s probably not as big of a deal than blocking, say, GitHub for a LAN with multiple tech-savvy users.I disagree. I’ll grant you they made a clear decision (and quickly), but didn’t explain further. Frankly I found their replies a bit confusing; they implied the issue as entirely about OEM/white-labeling and avoided the tracking/phone home question. They should just clarify why the badge actually exists when the question came up the second time.
Agreed that maintaining a fork is work. But, I mean, check mine out, please. It’s 3 lines, and could probably be reduced to a few characters. I’d still love to avoid the fork because your other reasons are quite valid, especially about trust. That’s what this is really about, to be honest. I don’t trust this isn’t a phone home, and I don’t want to have to trust them on this.
100% agreed.
I don’t understand. Will you explain what you mean here?
If you mean badges on GitHub repo home pages then yes, I agree.
If you mean mandatory phoning home or, really, reaching out for any images/static assets from a self-hosted service, I disagree.
Here’s the right way to do it (again, assuming this is a phone home): be 100% transparent that/if it is a phone home, have a privacy policy around data collected, and make it disabled by default. Traefik does this, for example. They have a phone home called
TRAEFIK_GLOBAL_SENDANONYMOUSUSAGE
that defaults tofalse
. Note the especially privacy-concerned (and perhaps less upgradae-concerned?) may wish to disableTRAEFIK_GLOBAL_CHECKNEWVERSION
as well.I never claimed it was. Maybe my fork will have security improvements as well someday, but right now it just has this one tiny patch. And I agree: best case is this fork becomes unnecessary (as transparency around the badge increases).
just_another_person@lemmy.world 4 months ago
Friend, please listen to reason.
The “code” you linked to is not functional code of any sort. Not to be nitpicky, it’s just an HTML image tag, so its Markup at best. All you did was stop the loading of an SVG image. The fact that they source it from their own domain tells you everything: they have a script that runs to check the current number of stars, then generates this image that reflects. It’s really standard.
All your other points you’re making because you do not have much experience in the software realm, which I’m not saying to be dismissive or anything like at all, I’m simply illustrating that all the points you’re questioning or mentioning are 100% standard.
Also, you might want to freak out about the social badges being sourced in this as well.