Re: atftpd permission denied

2025-04-11 Thread Michael Stone
On Fri, Apr 11, 2025 at 05:49:28PM -0400, Timothy M Butterworth wrote: Do you know if there is a setting in VSFTPD to upload files? /etc/vsftpd.conf: write_enable=YES

Re: atftpd permission denied

2025-04-11 Thread Timothy M Butterworth
On Fri, Apr 11, 2025 at 11:30 AM Michael Stone wrote: > On Thu, Apr 10, 2025 at 06:11:31PM -0400, Timothy M Butterworth wrote: > >I am having problems writing to atftpd. I keep getting a permission denied > >error. > > It sounds like you've worked around this

Re: atftpd permission denied

2025-04-11 Thread Timothy M Butterworth
On Fri, Apr 11, 2025 at 11:30 AM Michael Stone wrote: > On Thu, Apr 10, 2025 at 06:11:31PM -0400, Timothy M Butterworth wrote: > >I am having problems writing to atftpd. I keep getting a permission denied > >error. > > It sounds like you've worked around this

Re: atftpd permission denied

2025-04-11 Thread Michael Stone
On Thu, Apr 10, 2025 at 06:11:31PM -0400, Timothy M Butterworth wrote: I am having problems writing to atftpd. I keep getting a permission denied error. It sounds like you've worked around this, but I'll note for future searchers that the reason for this is that atftpd is confi

Re: atftpd permission denied

2025-04-11 Thread Dan Ritter
Timothy M Butterworth wrote: > On Thu, Apr 10, 2025 at 7:14 PM Dan Ritter wrote: > > > Timothy M Butterworth wrote: > > > All, > > > > > > I am having problems writing to atftpd. I keep getting a permission > > denied > > > error. > &g

Re: atftpd permission denied

2025-04-11 Thread Lee
On Thu, Apr 10, 2025 at 10:12 PM Timothy M Butterworth wrote: > > On Thu, Apr 10, 2025 at 7:14 PM Dan Ritter wrote: >> >> Timothy M Butterworth wrote: >> > All, >> > >> > I am having problems writing to atftpd. I keep getting a permission denied >&g

Re: atftpd permission denied

2025-04-10 Thread Timothy M Butterworth
On Fri, Apr 11, 2025 at 2:12 AM Titus Newswanger wrote: > > On 4/10/25 18:49, Timothy M Butterworth wrote: > > > I am trying to copy a Cisco IOS image from a switch so I can push it to > another switch. > > Sounds like the type of application where I tend to use scp. Would that do > the job? Or m

Re: atftpd permission denied

2025-04-10 Thread Titus Newswanger
On 4/10/25 18:49, Timothy M Butterworth wrote: I am trying to copy a Cisco IOS image from a switch so I can push it to another switch. Sounds like the type of application where I tend to use scp. Would that do the job? Or maybe I misunderstood your question. needs ssh access on remote dev

Re: atftpd permission denied

2025-04-10 Thread Timothy M Butterworth
On Thu, Apr 10, 2025 at 7:14 PM Dan Ritter wrote: > Timothy M Butterworth wrote: > > All, > > > > I am having problems writing to atftpd. I keep getting a permission > denied > > error. > > > > Switch#$.SED.bin tftp:// > 169.254.180.65/c3550-ipservic

Re: atftpd permission denied

2025-04-10 Thread Dan Ritter
Timothy M Butterworth wrote: > All, > > I am having problems writing to atftpd. I keep getting a permission denied > error. > > Switch#$.SED.bin tftp://169.254.180.65/c3550-ipservicesk9-mz.122-25.SED.bin > > > Address or name of remote host [169.254.180.65]? &g

atftpd permission denied

2025-04-10 Thread Timothy M Butterworth
All, I am having problems writing to atftpd. I keep getting a permission denied error. Switch#$.SED.bin tftp://169.254.180.65/c3550-ipservicesk9-mz.122-25.SED.bin Address or name of remote host [169.254.180.65]? Destination filename [c3550-ipservicesk9-mz.122-25.SED.bin]? ! TFTP: error code 2

Re: MiniDLNA log file permission problem

2024-02-17 Thread Kushal Kumaran
On Sat, Feb 17 2024 at 01:34:05 PM, Lothar Braun wrote: > Hi, > > I'm debugging a permission problem with the log files created by > minidlna in /var/log/minidlna. I'm trying to use a different username > to run minidlna and do not use the default user account minidlna.

Re: MiniDLNA log file permission problem

2024-02-17 Thread Greg Wooledge
On Sat, Feb 17, 2024 at 01:34:05PM +0100, Lothar Braun wrote: > I'm debugging a permission problem with the log files created by minidlna in > /var/log/minidlna. I'm trying to use a different username to run minidlna and > do not use the default user account minidlna. The

Re: Unexpected permission denied

2023-01-26 Thread Max Nikulin
On 26/01/2023 11:04, Greg Wooledge wrote: On Thu, Jan 26, 2023 at 10:26:34AM +0700, Max Nikulin wrote: Greg, I agree with your warnings. Just out of curiosity, is there a reason why the following variant may still be unsafe? runas() { local who=$1; shift; su --login "$who" --shell=/bin/bash --c

Re: Unexpected permission denied

2023-01-25 Thread Greg Wooledge
On Thu, Jan 26, 2023 at 10:26:34AM +0700, Max Nikulin wrote: > Greg, I agree with your warnings. Just out of curiosity, is there a reason > why the following variant may still be unsafe? > > runas() { local who=$1; shift; su --login "$who" --shell=/bin/bash > --command='"$0" "$@"' -- "$@"; } 1) h

Re: Unexpected permission denied

2023-01-25 Thread Max Nikulin
On 25/01/2023 21:52, Greg Wooledge wrote: On Wed, Jan 25, 2023 at 03:36:33PM +0100, Yassine Chaouche wrote: runas_wwwdata () { echo su - www-data -s /bin/bash -c "$*"; su - www-data -s /bin/bash -c "$*" } ... su(1) is pretty much the WORST possible choice for this, as it forces you t

Re: Unexpected permission denied

2023-01-25 Thread Jeffrey Walton
On Wed, Jan 25, 2023 at 2:54 AM jeremy ardley wrote: > > [...] > Rechecked, thanks. The vendor directory didn't have x permissions. > Fixed. Now to track down all the other files similarly afflicted in the > screaming pile of manure called drupal. > > root@gram01:/# ls -ld var/www/grammartiste.com

Re: Unexpected permission denied

2023-01-25 Thread Jeffrey Walton
On Wed, Jan 25, 2023 at 2:34 AM wrote: > > On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote: > > [...] > > > 0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php", > > 0x7fffdc580970) = -1 EACCES (Permission deni

Re: Unexpected permission denied

2023-01-25 Thread Nicolas George
Greg Wooledge (12023-01-25): > When investigating permissions, there's really no reason to do the > investigation as a non-root user. When investigating permissions, doing your tests as root instead of the user who is having the permissions issues, is a sure way for hiding the issue. Nothing to a

Re: Unexpected permission denied

2023-01-25 Thread Greg Wooledge
On Wed, Jan 25, 2023 at 03:36:33PM +0100, Yassine Chaouche wrote: > Le 1/25/23 à 3:22 PM, Nicolas George a écrit : > > For the current problem: > > > > sudo -u www-data namei /var/www/nextcloud/3rdparty/autoload.php > > > > … will cause the command to be executed in an environment closer to the >

Re: Unexpected permission denied

2023-01-25 Thread Yassine Chaouche
Le 1/25/23 à 3:22 PM, Nicolas George a écrit : For the current problem: sudo -u www-data namei /var/www/nextcloud/3rdparty/autoload.php … will cause the command to be executed in an environment closer to the one that causes the problem, and therefore is more likely to reveal it. Use any command

Re: Unexpected permission denied

2023-01-25 Thread Nicolas George
Yassine Chaouche (12023-01-25): > I prefer to use namei -l. namei is good indeed. > root@cloud[10.10.10.84/24] 15:15:43 ~ # namei -l > /var/www/nextcloud/3rdparty/autoload.php For the current problem: sudo -u www-data namei /var/www/nextcloud/3rdparty/autoload.php … will cause the command to

Re: Unexpected permission denied

2023-01-25 Thread Yassine Chaouche
friends. You've got ACLs, getfacl(1) and friends. You've got AppArmor, which can cause Permission denied errors on files outside of a program's designated working areas. This usually crops up when someone tries to move stuff to a different location in the file system(s) with a

Re: Unexpected permission denied

2023-01-25 Thread Yassine Chaouche
Le 1/25/23 à 8:44 AM, jeremy ardley a écrit : Anyway tree permissions: root@gram01:/# ls -ld var drwxr-xr-x 12 root root 4096 Nov  7 23:30 var root@gram01:/# ls -ld var/www drwxr-xr-x 5 www-data www-data 4096 Jan 23 16:33 var/www root@gram01:/# ls -ld var/www/grammartiste.com/ drwxr-xr-

Re: Unexpected permission denied

2023-01-25 Thread Thomas Schmitt
Hi, jeremy ardley wrote: > > > I have vague memories there are more file flags in newer Linux file > > > systems? Dan Ritter wrote: > > There are extended attributes, [...] > > lsattr and chattr are the relevant commands. Nicolas George wrote: > What you describe are file attributes specific to

Re: Unexpected permission denied

2023-01-25 Thread Greg Wooledge
ends. You've got ACLs, getfacl(1) and friends. You've got AppArmor, which can cause Permission denied errors on files outside of a program's designated working areas. This usually crops up when someone tries to move stuff to a different location in the file system(s) with a symlin

Re: Unexpected permission denied

2023-01-25 Thread Nicolas George
Dan Ritter (12023-01-25): > There are extended attributes, of which the only one you are > likely to encounter is i, immutable. It is occasionally useful > to nail down the state of a file even when something properly > has write permissions for it. > > lsattr and chattr are the relevant commands.

Re: Unexpected permission denied

2023-01-25 Thread Dan Ritter
jeremy ardley wrote: > I have vague memories there are more file flags in newer Linux file systems? There are extended attributes, of which the only one you are likely to encounter is i, immutable. It is occasionally useful to nail down the state of a file even when something properly has write p

Re: Unexpected permission denied

2023-01-25 Thread tomas
On Wed, Jan 25, 2023 at 03:53:50PM +0800, jeremy ardley wrote: [...] > Rechecked, thanks. The vendor directory didn't have x permissions. Fixed. > Now to track down all the other files similarly afflicted in the screaming > pile of manure called drupal. uh-oh ;-) Cheers & good luck -- t sign

Re: Unexpected permission denied

2023-01-24 Thread jeremy ardley
On 25/1/23 15:44, jeremy ardley wrote: On 25/1/23 15:33, to...@tuxteam.de wrote: On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote: [...]   0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php", 0x7fffdc580970) = -1 EACCES (Permission denied)

Re: Unexpected permission denied

2023-01-24 Thread jeremy ardley
On 25/1/23 15:33, to...@tuxteam.de wrote: On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote: [...] 0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php", 0x7fffdc580970) = -1 EACCES (Permission denied) 0.34 lstat("/var/www/grammartiste

Re: Unexpected permission denied

2023-01-24 Thread tomas
On Wed, Jan 25, 2023 at 02:51:05PM +0800, jeremy ardley wrote: [...] > 0.41 lstat("/var/www/grammartiste.com/web/vendor/autoload.php", > 0x7fffdc580970) = -1 EACCES (Permission denied) > 0.34 lstat("/var/www/grammartiste.com/web/vendor/autoload.php&q

Unexpected permission denied

2023-01-24 Thread jeremy ardley
.29 stat("/var/www/grammartiste.com/web/index.php", {st_mode=S_IFREG|0755, st_size=549, ...}) = 0 0.34 getcwd("/var/www/grammartiste.com/web", 4096) = 30 0.30 stat("/var/www/grammartiste.com/web/autoload.php", {st_mode=S_IFREG|0755, st_size=312

Re: Disable systemd script just by removing execute permission?

2022-07-01 Thread Greg Wooledge
) tlp resume ;; > > > esac > > > > > > I don't want to uninstall tlp altogether, so I have removed execute > > > permission from this script: > > > > > > $ ls -l /usr/lib/systemd/system-sleep/tlp > > > -rw-r--r-- 1 root root 239 Feb

Re: Disable systemd script just by removing execute permission?

2022-06-30 Thread Greg Wooledge
> case $1 in > pre) tlp suspend ;; > post) tlp resume ;; > esac > > I don't want to uninstall tlp altogether, so I have removed execute > permission from this script: > > $ ls -l /usr/lib/systemd/system-sleep/tlp > -rw-r--r-- 1 root root 239 Feb 3 15:0

Re: Question on permission denied (public key)

2021-12-06 Thread john doe
: git config --global user.email "n...@mail.com" git config --global user.name "new-username" After doing those when I run git pull it always gets: $ git pull Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the corre

Question on permission denied (public key)

2021-12-06 Thread Adriel Peng
uot;n...@mail.com" git config --global user.name "new-username" After doing those when I run git pull it always gets: $ git pull Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository ex

Re: Impossible to give "write" permission on a sub folder

2021-11-29 Thread David Wright
On Mon 29 Nov 2021 at 23:26:53 (+0100), lists.deb...@netc.eu wrote: > [ … ] I have always been a Windows user, but for a while I've been thinking > in changing to Linux. Last month I decided to do the change, but as we are 2 > people at home (me and my wife), I've decided to do a dual boot while

Re: Impossible to give "write" permission on a sub folder

2021-11-29 Thread lists . debian
PC-01\Admin AUTORITE NT\Système Allow FullControl > BUILTIN\Administrateurs Allow FullControl > PC-01\Admin Allow FullControl > PC-01\user1 Allow FullControl > PC-01\user2 Allow FullControl > Tout le monde Allow Write, ReadAndExecute, Synchronize > > PS D:\Documents\User1> If I

Re: Impossible to give "write" permission on a sub folder

2021-11-28 Thread David Wright
On Sun 28 Nov 2021 at 17:45:33 (+0100), lists.deb...@netc.eu wrote: > Thansk for the answer. To be honest to you, I already checked all that. Both > User1 and User2 folders have have exactly the same permission sets on Windows > (they both herit them from the Documents folder). We

Re: Impossible to give "write" permission on a sub folder

2021-11-28 Thread lists . debian
Thansk for the answer. To be honest to you, I already checked all that. Both User1 and User2 folders have have exactly the same permission sets on Windows (they both herit them from the Documents folder). I did also tried to use the usermap file, but I must say that I didn't managed to do

Re: Impossible to give "write" permission on a sub folder

2021-11-27 Thread Chuck Zmudzinski
/windows, all with the correct permission settings (rwx) : $ ls -l /mnt/windows/ total 80 drwxrwxrwx 1 root root 4096 14 nov. 20:20 '$RECYCLE.BIN' drwxrwxrwx 1 root root 4096 24 nov. 15:59 CloudStation drwxrwxrwx 1 root root 4096 21 nov. 11:44 Documents -rwxrwxrwx 1

Re: Impossible to give "write" permission on a sub folder

2021-11-27 Thread Andrew M.A. Cater
orrect permission settings (rwx) : $ ls -l /mnt/windows/ > > total 80 > > drwxrwxrwx 1 root root 4096 14 nov. 20:20 '$RECYCLE.BIN' drwxrwxrwx 1 root root 4096 24 nov. 15:59 CloudStation drwxrwxrwx 1 root root 4096 21 nov. 11:44 Documents > > -rwxrwxrwx 1 root root 81

Re: Impossible to give "write" permission on a sub folder

2021-11-26 Thread David
On Sat, 27 Nov 2021 at 09:20, Charles Curley wrote: > On Fri, 26 Nov 2021 15:50:04 -0500 Kenneth Parker wrote: > Correct, there are two parts. One is plain text, and all scrunched into > an unreadable blob. The other is HTML, and is at least readable. > > I am on Gmail, and got something that l

Re: Impossible to give "write" permission on a sub folder

2021-11-26 Thread Charles Curley
On Fri, 26 Nov 2021 15:50:04 -0500 Kenneth Parker wrote: > > Presumably there is also an HTML part which is actually > > comprehensible to humans. I didn't check, but it's a fair > > assumption. Correct, there are two parts. One is plain text, and all scrunched into an unreadable blob. The othe

Re: Impossible to give "write" permission on a sub folder

2021-11-26 Thread Kenneth Parker
On Fri, Nov 26, 2021, 2:37 PM Greg Wooledge wrote: > On Fri, Nov 26, 2021 at 07:30:32PM +, Brian wrote: > > On Fri 26 Nov 2021 at 09:29:50 +0100, lists.deb...@netc.eu wrote: > > > > > Hello to all, I have a dual boot PC with Windows 10 and Debian 11 This > PC has 2 drives, one SSD that has bo

Re: Impossible to give "write" permission on a sub folder

2021-11-26 Thread David Christensen
and Debian. To do it, I added the following line to the fstab file: UUID=ACB23705B236D414 /mnt/windows    ntfs-3g defaults,umask=000  0   0 the folders lount without any problem to /mnt/windows, all with the correct permission settings (rwx) : $ ls -l /mnt/windows/ total

Re: Impossible to give "write" permission on a sub folder

2021-11-26 Thread Greg Wooledge
On Fri, Nov 26, 2021 at 07:30:32PM +, Brian wrote: > On Fri 26 Nov 2021 at 09:29:50 +0100, lists.deb...@netc.eu wrote: > > > Hello to all, I have a dual boot PC with Windows 10 and Debian 11 This PC > > has 2 drives, one SSD that has both operating systems and a HDD where I > > store all oth

Re: Impossible to give "write" permission on a sub folder

2021-11-26 Thread Brian
to share this HDD > between Windows and Debian. To do it, I added the following line to the fstab > file: > > UUID=ACB23705B236D414 /mnt/windows ntfs-3g defaults,umask=000 0 0 > > the folders lount without any problem to /mnt/windows, all with the correct > permission set

Re: Impossible to give "write" permission on a sub folder

2021-11-26 Thread rhkramer
nt without any problem to > /mnt/windows, all with the correct permission settings (rwx) : > > $ ls -l > /mnt/windows/ > > total 80 > > drwxrwxrwx 1 root root 4096 14 nov. 20:20 > '$RECYCLE.BIN' > > drwxrwxrwx 1 root root 4096 24 nov. 15:59 CloudStation

Impossible to give "write" permission on a sub folder

2021-11-26 Thread lists . debian
to the fstab file: > > UUID=ACB23705B236D414 /mnt/windows ntfs-3g defaults,umask=000 0 0 > the folders lount without any problem to /mnt/windows, all with the correct permission settings (rwx) : > > $ ls -l /mnt/windows/ > > total 80 > > drwxrwxrwx 1 root root 4096

Re: Permission Questions

2021-08-31 Thread Rainer Dorsch
t;> /tmp/123' > > > [...] > > > openat(AT_FDCWD, "/tmp/123", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 > > > EACCES (Permission denied) > > > > > > As far as I can see, this is a kernel bug. Unless I'm overlooking > > > somethin

Re: Permission Questions

2021-08-30 Thread Rainer Dorsch
to the file as a > > test: > > > > -rw-rw-r-- 1 rd users 0 30. Aug 20:35 /tmp/123 > > > > ka@h370:~$ id > > uid=1401(ka) gid=1401(ka) Gruppen=1401(ka),20(dialout),21(fax),24(cdrom), > > 30(dip),44(video),46(plugdev),100(users),1000(sispmctl) > > ka

Permission Questions

2021-08-30 Thread Rainer Dorsch
drom), 30(dip),44(video),46(plugdev),100(users),1000(sispmctl) ka@h370:~$ ls -l /tmp/123 -rw-rw-r-- 1 rd users 0 30. Aug 20:35 /tmp/123 ka@h370:~$ echo test >> /tmp/123 -bash: /tmp/123: Permission denied ka@h370:~$ Even that does not work. Why not? Is there something special with /

Re: Permission Questions

2021-08-30 Thread Greg Wooledge
On Mon, Aug 30, 2021 at 09:29:14PM +, Andy Smith wrote: > Hello, > > On Mon, Aug 30, 2021 at 05:07:16PM -0400, Greg Wooledge wrote: > > unicorn:~$ strace bash -c 'echo stuff >> /tmp/123' > > [...] > > openat(AT_FDCWD, "/tmp/123", O_WRONLY

Re: Permission Questions

2021-08-30 Thread Andy Smith
Hello, On Mon, Aug 30, 2021 at 05:07:16PM -0400, Greg Wooledge wrote: > unicorn:~$ strace bash -c 'echo stuff >> /tmp/123' > [...] > openat(AT_FDCWD, "/tmp/123", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 EACCES > (Permission denied) > > As far as

Re: Permission Questions

2021-08-30 Thread Greg Wooledge
tly as other users? unicorn:~$ ls -l /tmp/123 -rw-rw-r-- 1 daemon video 0 Aug 30 17:00 /tmp/123 unicorn:~$ echo stuff >> /tmp/123 bash: /tmp/123: Permission denied That is interesting! unicorn:~$ strace bash -c 'echo stuff >> /tmp/123' [...] openat(AT_FDCWD, "/tmp/123"

Re: Permission Questions

2021-08-30 Thread Greg Wooledge
ialout),21(fax),24(cdrom), > 30(dip),44(video),46(plugdev),100(users),1000(sispmctl) > ka@h370:~$ ls -l /tmp/123 > -rw-rw-r-- 1 rd users 0 30. Aug 20:35 /tmp/123 > ka@h370:~$ echo test >> /tmp/123 > -bash: /tmp/123: Permission denied That one should have worked, due to the s

Re: Permission Questions

2021-08-30 Thread IL Ka
> > > Is there something special with /tmp? > Do you have sticky bit on `/tmp`? > For directories, when a directory's sticky bit is set, the filesystem treats the files in such directories in a special way so only the file's owner, the directory's owner, or root user can rename or delete the file

Re: debian discover (naturally) lacks permission to install software, how to proceed

2020-03-20 Thread Dan Hitt
On Fri, Mar 20, 2020 at 4:40 PM songbird wrote: > Dan Hitt wrote: > > > I'm in the process of seeing if i can install a zoom client on my debian > 10 > > system. > ... > > this sounds like a really good way to mess up a system. > > google had the answer as the top result. no idea if it > wor

Re: debian discover (naturally) lacks permission to install software, how to proceed

2020-03-20 Thread songbird
Dan Hitt wrote: > I'm in the process of seeing if i can install a zoom client on my debian 10 > system. ... this sounds like a really good way to mess up a system. google had the answer as the top result. no idea if it works as i don't use such a thing myself. https://support.zoom.us/hc

debian discover (naturally) lacks permission to install software, how to proceed

2020-03-20 Thread Dan Hitt
I'm in the process of seeing if i can install a zoom client on my debian 10 system. There's a deb file for it, zoom_amd64.deb, but i would like to see if i can do it using the gui: in firefox, when i click on the download link, i get a little window that says "What should Firefox do with this file

Re: Re: Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied

2019-07-17 Thread Simon Bernier St-Pierre
Thanks a ton! I'm running this container on my private network behind a NAT, so I'm not too worried about disabling apparmor. I ended up just giving as loose of a configuration I could and it did the trick. lxc.apparmor.profile = unconfined lxc.apparmor.allow_nesting = 1 lxc.apparmor.allow_in

Re: Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied

2019-07-17 Thread Reco
to the problem. > This is the journalctl log for the openvpn service: ... > Jul 16 20:32:30 dl systemd[70]: openvpn-client@pia.service: Failed to > set up mount namespacing: Permission denied And that is too. As usual with this kind of problems, journalctl log is useless. What you need

Issue with OpenVPN inside a LXC container: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied

2019-07-16 Thread Simon Bernier St-Pierre
0:32:30 dl systemd[70]: openvpn-client@pia.service: Failed to set up mount namespacing: Permission denied Jul 16 20:32:30 dl systemd[70]: openvpn-client@pia.service: Failed at step NAMESPACE spawning /usr/sbin/openvpn: Permission denied Jul 16 20:32:30 dl systemd[1]: openvpn-client@pia.service: Ma

Re: bind gets permission errors in buster--systemd-related?

2019-05-15 Thread Ross Boylan
On Wed, May 15, 2019 at 10:39 AM Sven Joachim wrote: > I am not really familiar with apparmor or resolvconf, but in > /etc/apparmor.d/usr.sbin.named I found the following: > > , > | # support for resolvconf > | /{,var/}run/named/named.options r, > ` > > which suggests that the sta

Re: bind gets permission errors in buster--systemd-related?

2019-05-15 Thread Bob Weber
I also have a similar problem accessing /run/named.  bind can't create the directory or any files in it.  The error messages: couldn't mkdir '//run/named': Permission denied could not create //run/named/session.key Apparmor problems can be fixed by running aa-logprof an

Re: bind gets permission errors in buster--systemd-related?

2019-05-15 Thread Sven Joachim
On 2019-05-15 09:33 -0700, Ross Boylan wrote: > Sven, thanks for the tip about AppArmor. Yet another presumably > complicated system I've avoided learning about til now. I guess it's > time. > > As to why bind is trying to open /run/named/named.resolvers: that is a > customized integration with

Re: bind gets permission errors in buster--systemd-related?

2019-05-15 Thread Greg Wooledge
On Wed, May 15, 2019 at 12:11:58PM -0400, Lee wrote: > The way I fixed my permission problems after telling bind to log to a > file instead of syslog was > su - > to become root > su bind > which didn't work because > # grep bind /etc/passwd > bind:x:116:11

Re: bind gets permission errors in buster--systemd-related?

2019-05-15 Thread Ross Boylan
omething I want to work. Or I need an alternate way to achieve the same functionality, which is that when resolvconf gets info on nameservers it passes that on to bind. Lee, I don't think this is a vanilla permission problem. As I thought the comments in the original indicated, ownership

Re: bind gets permission errors in buster--systemd-related?

2019-05-15 Thread Lee
and in both cases this > failed with permission problems. > I'm pretty sure bind is running under systemd, and have seen various > references to systemd limiting access to the file system. However, I > don't see anything that appears to be requesting such limits for >

Re: bind gets permission errors in buster--systemd-related?

2019-05-15 Thread Sven Joachim
bind proper, and in both cases this > failed with permission problems. > I'm pretty sure bind is running under systemd, and have seen various > references to systemd limiting access to the file system. However, I > don't see anything that appears to be requesting such limits

bind gets permission errors in buster--systemd-related?

2019-05-14 Thread Ross Boylan
I have a new buster system with a bind setup based on (much) older* systems, on which it worked fine. On buster, it doesn't. In two different places in my configuration I referred to files or directories that were outside of bind proper, and in both cases this failed with permission problems

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-17 Thread Reco
Hi. On Thu, Oct 18, 2018 at 06:11:13AM +0200, steve wrote: > Le 17-10-2018, à 09:52:06 +0300, Reco a écrit : > > > > > And, finally, /var/log/audit/audit.log if you have auditd installed > > > > (hint - install it if you don't). > > > > > > grep apache /var/log/audit/audit.log > > > > >

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-17 Thread mick crane
On 2018-10-18 07:15, steve wrote: Le 18-10-2018, à 07:07:34 +0100, mick crane a écrit : On 2018-10-18 05:11, steve wrote: Still reading on this new thing for me. Thanks Steve I never came across this apparmor. did you try stopping it with systemctl then see if apache works as expected ?

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-17 Thread mick crane
On 2018-10-18 07:07, mick crane wrote: On 2018-10-18 05:11, steve wrote: Still reading on this new thing for me. Thanks Steve I never came across this apparmor. did you try stopping it with systemctl then see if apache works as expected ? Ah, OK I see you tried that. Would that not indi

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-17 Thread steve
Le 18-10-2018, à 07:07:34 +0100, mick crane a écrit : On 2018-10-18 05:11, steve wrote: Still reading on this new thing for me. Thanks Steve I never came across this apparmor. did you try stopping it with systemctl then see if apache works as expected ? Yes I did and apache failed to s

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-17 Thread mick crane
On 2018-10-18 05:11, steve wrote: Still reading on this new thing for me. Thanks Steve I never came across this apparmor. did you try stopping it with systemctl then see if apache works as expected ? mick -- Key ID4BFEBB31

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-17 Thread steve
Le 17-10-2018, à 09:52:06 +0300, Reco a écrit : > And, finally, /var/log/audit/audit.log if you have auditd installed > (hint - install it if you don't). grep apache /var/log/audit/audit.log type=AVC msg=audit(1539750555.347:76): apparmor="DENIED" operation="open" profile="/usr/sbin/apache2"

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-17 Thread steve
Thanks Reco for your input. I'll have to go trough it, but don't have time right now. Steve

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-17 Thread steve
Le 17-10-2018, à 05:38:11 +, Steve Kemp a écrit : To recap you reported the original error: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied Now you've provided more details, from your audit-log: type=AVC msg=audit(1539750555.3

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Reco
:22:01 box systemd[1]: Starting The Apache HTTP Server... > > > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open > > > configuration file /etc/apache2/apache2.conf: Permission denied > > > oct 16 07:22:02 box apachectl[32122]: Action 'start' failed.

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Steve Kemp
To recap you reported the original error: > apache2: Could not open configuration file /etc/apache2/apache2.conf: > Permission denied Now you've provided more details, from your audit-log: > type=AVC msg=audit(1539750555.347:77): apparmor="DENIED" > operatio

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread steve
Le 16-10-2018, à 06:39:01 +, Steve Kemp a écrit : ls -l /etc/apache2/apache2.conf -rw-r--r-- 1 root root 7224 jun 2 10:01 /etc/apache2/apache2.conf Getting nuts. Probably the permissions on /etc/apache2, or /etc are broken for the user www-data. ls -l /etc drwxr-xr-x 213 root root

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread steve
rting The Apache HTTP Server... oct 16 07:22:01 box apachectl[32122]: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. oct 16 07:22:02 box apachectl[32122]: The Apache error log may have mo

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread David Wright
On Tue 16 Oct 2018 at 12:24:49 (-0400), Gene Heskett wrote: > On Tuesday 16 October 2018 11:37:44 Greg Wooledge wrote: > > > On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote: > > > Since leaving a sudo -i laying about is considered a security > > > breach, I'm amazed that the -i option

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Gene Heskett
On Tuesday 16 October 2018 11:37:44 Greg Wooledge wrote: > On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote: > > Since leaving a sudo -i laying about is considered a security > > breach, I'm amazed that the -i option doesn't accept a timeout. Say > > in seconds, as if you think it will

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Gene Heskett
On Tuesday 16 October 2018 11:37:44 Greg Wooledge wrote: > On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote: > > Since leaving a sudo -i laying about is considered a security > > breach, I'm amazed that the -i option doesn't accept a timeout. Say > > in seconds, as if you think it will

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Greg Wooledge
On Tue, Oct 16, 2018 at 11:28:44AM -0400, Gene Heskett wrote: > Since leaving a sudo -i laying about is considered a security breach, I'm > amazed that the -i option doesn't accept a timeout. Say in seconds, as > if you think it will take 5 minutes to do the job as root, sudo -i300, > at the end

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Gene Heskett
On Tuesday 16 October 2018 05:56:31 Jonathan Dowland wrote: > On Tue, Oct 16, 2018 at 10:09:39AM +0200, Martin wrote: > >> sudo su - www-data -s /bin/sh > > > >Don't use sudo with su. It is evil. > >You want to use 'sudo -i' in this case. > > Fascism is evil. This is just unnecessary. > > (I'm

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Martin
Am 16.10.18 um 11:56 schrieb Jonathan Dowland: > On Tue, Oct 16, 2018 at 10:09:39AM +0200, Martin wrote: >>>     sudo su - www-data -s /bin/sh >> >> Don't use sudo with su. It is evil. >> You want to use 'sudo -i' in this case. > > Fascism is evil. This is just unnecessary. Good point. > > (I'm

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Jonathan Dowland
On Tue, Oct 16, 2018 at 10:09:39AM +0200, Martin wrote: sudo su - www-data -s /bin/sh Don't use sudo with su. It is evil. You want to use 'sudo -i' in this case. Fascism is evil. This is just unnecessary. (I'm guilty of still typing "sudo su -" via muscle memory even after your messages

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Joe
o Process: 32122 > > ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE) > > > > oct 16 07:22:01 box systemd[1]: Starting The Apache HTTP Server... > > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open > > configuration file /etc/apache2/apa

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Martin
Am 16.10.18 um 08:39 schrieb Steve Kemp: >> >> ls -l /etc/apache2/apache2.conf >> -rw-r--r-- 1 root root 7224 jun 2 10:01 /etc/apache2/apache2.conf [...] > sudo su - www-data -s /bin/sh Don't use sudo with su. It is evil. You want to use 'sudo -i' in this case. [...]

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-16 Thread Martin
box systemd[1]: Starting The Apache HTTP Server... > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open configuration > file /etc/apache2/apache2.conf: Permission denied > oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. > oct 16 07:22:02 box apachect

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-15 Thread Reco
01 box systemd[1]: Starting The Apache HTTP Server... > oct 16 07:22:01 box apachectl[32122]: apache2: Could not open configuration > file /etc/apache2/apache2.conf: Permission denied > oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. > oct 16 07:22:02 box apache

Re: apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-15 Thread Steve Kemp
> > ls -l /etc/apache2/apache2.conf > -rw-r--r-- 1 root root 7224 jun 2 10:01 /etc/apache2/apache2.conf > > > Getting nuts. Probably the permissions on /etc/apache2, or /etc are broken for the user www-data. Assuming you have sudo installed you can become "www-data", and test: sudo

apache2: Could not open configuration file /etc/apache2/apache2.conf: Permission denied

2018-10-15 Thread steve
ache2/apache2.conf: Permission denied oct 16 07:22:02 box apachectl[32122]: Action 'start' failed. oct 16 07:22:02 box apachectl[32122]: The Apache error log may have more information. oct 16 07:22:02 box systemd[1]: apache2.service: Control process exited, code=exited status=1 oct

Underlying problems - was [Re: Permission issues - operator error?]

2018-09-24 Thread Richard Owlett
On 09/22/2018 08:34 AM, Richard Owlett wrote: I'm assuming operator problem as I get same symptoms on:    two laptops each running different Debian releases (6.8, 9.1). [both using MATE desktop]    two different media (32Gb USB flash, 240 Gb USB SSD). Logged in as 'richard' I use Gparted

Re: Permission issues - operator error?

2018-09-23 Thread Richard Hector
On 24/09/18 1:20 AM, Richard Owlett wrote: > root@debian8-6:/home/richard# # force UID/GID to 'richard', label > device, accept standard defaults > root@debian8-6:/home/richard# mkfs.ext4 root_owner=1000:1000 -L > 2018Sept23tst1 /dev/sdb1 > mke2fs 1.42.12 (29-Aug-2014) > mkfs.ext4: invalid blocks '

  1   2   3   4   5   6   7   8   9   10   >