this post was submitted on 06 Jul 2024
372 points (91.2% liked)

Technology

57435 readers
3218 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
372
Signal under fire for storing encryption keys in plaintext on desktop app (stackdiary.com)
submitted 1 month ago by [email protected] to c/[email protected]
72 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 1 month ago (2 children)

I have a couple problems with it aside from being electron.

  1. On linux, whether it is a native package or flatpak. I have to launch it twice for it to open.

  2. I can't restore chats from my phone to the desktop application which frankly sucks. It makes sense if they don't wanna have to store extra data on their servers, but at least let the backups that I manually take on my phone be usable on the desktop. Not having the majority of your conversations from before you linked the desktop app is a pain in the arse.

[–] [email protected] 4 points 1 month ago (1 children)

I never have to launch twice on flatpak.

And I only keep conversations for 2 to 4 weeks so starting over doesn't bother me. Sorry if that doesn't work for you too.

[–] [email protected] 1 points 1 month ago (1 children)

I don't do temporary conversations, but this is the open issue on the flatpak https://github.com/flathub/org.signal.Signal/issues/454. The thing is, I'm having the same issue as the flatpak even though I'm not using the flatpak.

[–] [email protected] 1 points 1 month ago (1 children)

That sucks and they need to fix it. Still out hasn't happened here yet. Are you on Gnome desktop environment?

[–] [email protected] 1 points 1 month ago (1 children)

Nope, I'm on KDE.

[–] [email protected] 1 points 1 month ago (1 children)

I wonder if it's only happening on KDE? Either way, I'm sure it needs to be corrected.

[–] [email protected] 1 points 1 month ago

That would certainly be a weird one.

[–] [email protected] 1 points 1 month ago (1 children)

On linux, whether it is a native package or flatpak. I have to launch it twice for it to open.

Could it be yours is set to start in the tray?

[–] [email protected] 1 points 1 month ago (1 children)

Nope, its basically the same issue that the flatpak is happening, but I'm not using the flatpak. https://github.com/flathub/org.signal.Signal/issues/454

[–] [email protected] 1 points 1 month ago (1 children)

For me the january 13th solution seems to work, but I was doing that to begin with so I never noticed the issue. Signal flatpak, openSUSE Tumbleweed and KDE Plasma 6. Signal is started with --use-tray-icon --start-in-tray

[–] [email protected] 1 points 1 month ago

Glad that it works for you. I may have to switch over to the flatpak then.