[GH-ISSUE #290] No certificate fingerprint showing on the UI #145

New issue

Open

opened 2026-05-05 22:11:32 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 22:11:32 -06:00

Owner

Originally created by @mbinns on GitHub (May 2, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/290

When starting up the application everything seems to work fine and it can communicate to the other lan-mouse instances on my lan... But I am not seeing the fingerprint on one of the clients so I cannot add it as an authorized source on the other clients.

Please let me know if there is any other information I can provide, or just a place I can get the fingerprint on disk.

lan-mouse --version
lan-mouse 0.10.0-nixpkgs

Originally created by @mbinns on GitHub (May 2, 2025). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/290 When starting up the application everything seems to work fine and it can communicate to the other lan-mouse instances on my lan... But I am not seeing the fingerprint on one of the clients so I cannot add it as an authorized source on the other clients. Please let me know if there is any other information I can provide, or just a place I can get the fingerprint on disk. ![Image](https://github.com/user-attachments/assets/0fb9dcc0-e7bd-4191-97dc-3cebe7861e99) ``` lan-mouse --version lan-mouse 0.10.0-nixpkgs ```

gitea-mirror commented

2026-05-05 22:11:34 -06:00

Author

Owner

@sjagoe commented on GitHub (Sep 23, 2025):

The encryption appears to be in main and not yet in a "stable" release, so is not packaged on nixos.

I'm using the latest built from source with this in my flake.nix

lan-mouse = {
  url = "git+https://github.com/feschber/lan-mouse?ref=main&rev=e46fe60b3e24be83de38701faa99a4fbd9186f08";
  inputs.nixpkgs.follows = "nixpkgs";
};

and adding inputs.lan-mouse.packages.${pkgs.system}.lan-mouse to home packages (passing flake inputs via specialArgs.inputs = inputs;)

Sorry I can't share my actual configuration; it's in a repository containing private data.

@sjagoe commented on GitHub (Sep 23, 2025): The encryption appears to be in `main` and not yet in a "stable" release, so is not packaged on nixos. I'm using the latest built from source with this in my `flake.nix` ``` lan-mouse = { url = "git+https://github.com/feschber/lan-mouse?ref=main&rev=e46fe60b3e24be83de38701faa99a4fbd9186f08"; inputs.nixpkgs.follows = "nixpkgs"; }; ``` and adding `inputs.lan-mouse.packages.${pkgs.system}.lan-mouse` to home packages (passing flake `inputs` via `specialArgs.inputs = inputs;`) Sorry I can't share my actual configuration; it's in a repository containing private data.

gitea-mirror commented

2026-05-05 22:11:35 -06:00

Author

Owner

@fnchooft commented on GitHub (Oct 3, 2025):

Morning - can confirm this.
I just did a clean checkout on Ubuntu 24.04 ( default installation ).
Same rev as @sjagoe.

`
cargo build # All good

cargo package # Failed

error[E0432]: unresovled import 'lan_mouse_cli::CliArgs' -> src/config.rs:15.5
`

I still have the case where on one machine the share options are not offered. Not sure why.
But at least in main branch on both machine a pem-file is generated correctly without having to set up a config.toml file.

@fnchooft commented on GitHub (Oct 3, 2025): Morning - can confirm this. I just did a clean checkout on Ubuntu 24.04 ( default installation ). Same rev as @sjagoe. ` cargo build # All good cargo package # Failed error[E0432]: unresovled import 'lan_mouse_cli::CliArgs' -> src/config.rs:15.5 ` I still have the case where on one machine the share options are not offered. Not sure why. But at least in main branch on both machine a pem-file is generated correctly without having to set up a config.toml file.

gitea-mirror commented

2026-05-05 22:11:36 -06:00

Author

Owner

@feschber commented on GitHub (Oct 29, 2025):

Yes, the encryption feature is not released yet.

@fnchooft don't use cargo package afaik it locks the dependencies to their versions, which wont work since a lot has changed since the last release.

@feschber commented on GitHub (Oct 29, 2025): Yes, the encryption feature is not released yet. @fnchooft don't use `cargo package` afaik it locks the dependencies to their versions, which wont work since a lot has changed since the last release.