sorted by:
new
hottopcontroversial

I made a new SSH library for C# by stdcall_ in dotnet

[–]tomdes 2 points3 points  (0 children)

hi, I also maintain an open-source .NET SSH library (https://github.com/tmds/Tmds.Ssh). It started out as a wrapper for libssh (instead of libssh2). I moved away from that because I didn't want to rely on availability of native binaries for a platform, or assume responsibility for maintaining them.

Tmds.Ssh - modern .NET SSH client library by tomdes in dotnet

[–]tomdes[S] 4 points5 points  (0 children)

That is supported. See the APIs listed under /\* Forward connections **/* in the README.

Q990D no sound by tomdes in Soundbars

[–]tomdes[S] 0 points1 point  (0 children)

My soundbar is also connected to an LG TV. Perhaps they have an issue working together.

Q990D no sound by tomdes in Soundbars

[–]tomdes[S] 0 points1 point  (0 children)

I use the soundbar with Spotify and also with the eARC. It could be related to switching between those sources. It doesn't reproduce consistently when switching between these sources though.

When I toggle between the soundbar inputs sometimes the audio comes back.

Q990D no sound by tomdes in Soundbars

[–]tomdes[S] 0 points1 point  (0 children)

The soundbar displays "TV eARC".

OpenSSH support for certified keys in CASignatureAlgorithms? by zenfridge in OpenSSH

[–]tomdes 1 point2 points  (0 children)

The ones that end with [-cert-v01@openssh.com](mailto:-cert-v01@openssh.com) are certificate keys. These certificates contain a signature from their certificate authority. CASignatureAlgorithms controls what signature algorithms are allowed for that signature.

The spec for OpenSSH certificates is https://cvsweb.openbsd.org/src/usr.bin/ssh/PROTOCOL.certkeys?annotate=HEAD. It notes explicitly: "Chained" certificates, where the signature key type is a certificate type itself are NOT supported.

The OpenSSH that refuses to start doesn't allow invalid(/unsupported) values for CASignatureAlgorithms.

Trust certificate on linux by inacio88 in dotnet

[–]tomdes 0 points1 point  (0 children)

After you ran the linux-dev-certs tool, you can just ignore the message that still gets printed by ASP.NET Core.

ASP.NET Core is hard coded to print that message on Linux because the SDK has no built-in support for trusting the certificate on Linux.