Arch Linux

chrabyrd

Member

Registered: 2018-10-09

Posts: 11

[SOLVED] Incorrect permissions over SSH?

Hi all!

I have a system where, if I access it via keyboard and mouse I'm able to successfully access the bluetooth interface via `bluetoothctl`. If I remain logged in, and then ssh into the system as the same user account, I'm able to also successfully access the bluetooth interface via `bluetoothctl`.

However, if I do not access the system via keyboard and mouse, and log in only over ssh, I am unable to gain access to the bluetooth interface via `bluetoothctl`. Instead, I need to use `sudo bluetoothctl`. This is a problem because I'd like to gain access to a graphical session over vnc, but when I attempt to do so (I assume) it doesn't have correct permissions and fails to load the applet.

Here are the related sshd_config settings:

UsePAM yes
#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
PrintMotd no # pam does that
#PrintLastLog yes
#TCPKeepAlive yes
PermitUserEnvironment yes
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /run/sshd.pid
#MaxStartups 10:30:100
PermitTunnel yes
#ChrootDirectory none
#VersionAddendum none
PermitRootLogin yes

Thanks for any help!

Last edited by chrabyrd (2018-11-22 21:39:47)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,532

Website

Re: [SOLVED] Incorrect permissions over SSH?

I am unable to gain access to the bluetooth interface via `bluetoothctl`

What does happen?  An error message?  What is it?

And why have you started another thread on this?  You already had a thread on this exact same issue/

Last edited by Trilby (2018-11-22 20:07:42)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [SOLVED] Incorrect permissions over SSH?

And the thread title dos not describe the actual issue: https://wiki.archlinux.org/index.php/Co … ow_to_post

Moving to NC...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

chrabyrd

Member

Registered: 2018-10-09

Posts: 11

Re: [SOLVED] Incorrect permissions over SSH?

I am unable to gain access to the bluetooth interface via `bluetoothctl`

What does happen?  An error message?  What is it?

And why have you started another thread on this?  You already had a thread on this exact same issue/

Sorry! It's a similar issue but not the exact same, this is dealing with a singular user account. I do not get an error message immediately after entering the interface. However, when trying to run any command in the interface I'm met with: `No default controller available`

loqs

Member

Registered: 2014-03-06

Posts: 19,106

Re: [SOLVED] Incorrect permissions over SSH?

What are the Session_permissions when only logged in via ssh?
As an aside allowing root ssh login via password has lead to many systems being compromised.

chrabyrd

Member

Registered: 2018-10-09

Posts: 11

Re: [SOLVED] Incorrect permissions over SSH?

What are the Session_permissions when only logged in via ssh?
As an aside allowing root ssh login via password has lead to many systems being compromised.

[localbox@homebox ~]$ loginctl show-session $XDG_SESSION_ID
Id=12
User=1001
Name=localbox
Timestamp=Thu 2018-11-22 11:01:35 PST
TimestampMonotonic=950304194
VTNr=0
TTY=pts/0
Remote=yes
RemoteHost=10.0.0.246
Service=sshd
Scope=session-12.scope
Leader=4139
Audit=12
Type=tty
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=1542921526107350
IdleSinceHintMonotonic=9181307258
LockedHint=no

Also no worries about root ssh, that's an artifact from troubleshooting :-)

chrabyrd

Member

Registered: 2018-10-09

Posts: 11

Re: [SOLVED] Incorrect permissions over SSH?

What are the Session_permissions when only logged in via ssh?
As an aside allowing root ssh login via password has lead to many systems being compromised.

Thank you! This was the thread I needed! It turns out it was a polkit issue and adding `auth-polkit=false` to my NetworkManager.conf file did the trick.