undefined

points

by database641287 hours ago |

comments

by redrove6 hours ago|

[-]

Developing for macos, I’ve gotten bit by keychain consistency issues far too many times. It’s a mess.

by wpm6 hours ago|

parent|

[-]

So many of the keychain APIs are "deprecated" (read: marked as "we will nuke this API whenever we want") and have been for a decade or more, but have no replacement either.

A lot of the Security Framework came from Classic, hell, the idea of a keychain came from Classic! Just a mess.

by BaardFigur55 minutes ago|

prev|

[-]

I'm using WireGuard myself. Not on MacOS, but on Windows/Linux/Android. The reason I went with WireGuard to begin with, is due to how secure it suppsedly was. Having long standing unresolved issues like that is a bit worrying. I'm still most likely safe, but it's not exactly reassuring, either

by con6 hours ago|

prev|

[-]

I had this as well - funny enough I asked my local AI to "find the removed config" and it was able to restore everything.

by database641286 hours ago|

parent|

[-]

Lucky for you! I first ran into this before AI agents were a thing, so :(

by kalleboo43 minutes ago|

prev|

[-]

This literally just happened to me yesterday. Again.

by raverbashing4 hours ago|

prev|

[-]

There are features built for security nerds (like PGP/GPG, etc)

And features built for normal people

The overlap is very rare

by patrakov2 hours ago|

parent|

[-]

This is not a feature built for security nerds. This is a feature built for corporate compliance box tickers, and it works precisely as wanted in corporate environments, where all lost secrets can be easily replaced after visiting the helpdesk room personally.

by raverbashing2 hours ago|

parent|

[-]

True, there's that as well

by sysguest4 hours ago|

parent|

prev|

[-]

well but deletion isn't what even those "security nerds" would have expected...

by adastra224 hours ago|

parent|

[-]

Security nerd here. I would have expected it. But only in the sense that I have no faith in this industry to write secure software and protect from data loss.

by pjmlp3 hours ago|

parent|

[-]

I keep hoping better liability laws will force management to support doing it the right way, if not anything else than avoid hefty fines.

by cl3misch6 hours ago|

prev|

[-]

> The bug still exists to this day

You linked a commit and a Reddit post. Is there a proper Github issue as well?

by database641286 hours ago|

parent|

[-]

> You linked a commit and a Reddit post. Is there a proper Github issue as well?

It's funny you mentioned that. The GitHub repository is a mirror of https://git.zx2c4.com/wireguard-apple. You cannot create issues there. You're supposed to send a bug report to the mailing list, which is enough friction that none of us did so far.

by Barbing6 hours ago|

parent|

[-]

>enough friction that none of us did so far.

Emailed per https://news.ycombinator.com/item?id=50450200

Definitely still a bug right? Linked them to your parent comment.

Edit: oops sorry team, think you're on it (4d ago): https://github.com/whyredfire/wireguard-apple/commit/0bac142...

Guess it can serve as feedback on the friction when issues can't simply be opened though!

by database641286 hours ago|

parent|

[-]

> Definitely still a bug right? Linked them to your parent comment.

Thanks! Yes, it is still a bug.

> Edit: oops sorry team, think you're on it (4d ago)

I don't think @zx2c4 has seen this PR, and the author of the PR has not sent a bug report yet, so it's probably fine :P

by traceroute664 hours ago|

parent|

[-]

> Thanks! Yes, it is still a bug.

Its unfortunate no updates for Wireguard macOS have been pushed out for 3 years, App Store is still showing 1.0.16 as the latest version – as also confirmed on the Wireguard website at the latest version.

No doubt macOS APIs have moved on a lot in 3 years and so perhaps bugs that are being seen are simply a reflection of the lack of updates to keep up with API changes ? Just thinking aloud here, I don't know if the concept of OS API changes are applicable to this particular PR / bug.

by Barbing5 hours ago|

parent|

prev|

[-]

All right! :)

by encom5 hours ago|

parent|

prev|

[-]

>friction

I appreciate when both options exist, because I've passed on reporting so many bugs, because I refuse to create a Microsoft account to do it.

In fact, I don't understand how sending an email is high friction.

by database641284 hours ago|

parent|

[-]

> I've passed on reporting so many bugs, because I refuse to create a Microsoft account to do it.

99% of the time it's perfectly fine to just email the maintainer with a bug report and maybe a patch.

> In fact, I don't understand how sending an email is high friction.

Judging from the fact that after so many years, such a widespread (as seen in the Reddit post and here) issue still hasn't resulted in a single bug report in the mailing list, I'd say most people (including myself) do indeed consider using a mailing list to be higher friction.

If I'm not mistaken, unless you're already CC'ed by a participant, you'd have to subscribe to the whole mailing list just to receive notifications for a single thread. For an "issue" on a Git forge, participation is usually as easy as upvoting and then clicking the "Subscribe" button.

by encom4 hours ago|

parent|

[-]

Assuming you're already using MS Github. Anyway, even if I was, a lot of Github project require filling out an absurd Simon Says form. Or that scene from Indiana Jones where he takes a wrong step and falls through the floor. That's nothing to do with email or Microsoft specifically, it's just another reason I almost never bother reporting bugs. Talk about friction.

by database641283 hours ago|

parent|

[-]

Yeah, I hate these forms (issue templates) too. Every time I have to fill such a form, I always feel that they are discouraging me from writing the bug description in a natural, coherent way. I'd spend more effort to make sure the description is clear and contains all necessary information, if there's no issue template requirements.

by jeremyjh1 hours ago|

parent|

[-]

Yes, but most people won't. Most people will submit a bug report with important information missing that means we have to go back and forth. Also, there is often specific debugging information that people would not even know would be useful.

In the current age, its useful because AI will submit tickets using the CLI that don't use the form, so I can immediately close and lock them and go on living my life.

by andersonpico6 hours ago|

parent|

prev|

[-]

from his link:

  Edit (March 2025):
  Wireguard, to my surprise, has no bug tracking system like Jira or issue tracking area such as GitHub.
  If you want to see this fixed, the only way to instigate change is to write team@wireguard.com and jason@zx2c4.com.

by seanjhkwon10 minutes ago|

prev|

[-]

[flagged]