On 2024-01-18 21:33, Sylvain Saboua wrote:
I have been using KDE/Plasma on openbsd since last week-end.
Amongst other bugs, mostly minor, which I should also report,
there is this one : when opening an new instance of konsole,
Plasma's terminal emulator program, the fallback folder location
Le 2024-01-20 11:53, Rafael Sadowski a écrit :
On Thu Jan 18, 2024 at 03:33:48PM +0100, Sylvain Saboua wrote:
I have been using KDE/Plasma on openbsd since last week-end.
Amongst other bugs, mostly minor, which I should also report,
there is this one : when opening an new instance of konsole,
Le 2024-01-20 11:59, hahahahacker2...@airmail.cc a écrit :
On 2024-01-18 21:33, Sylvain Saboua wrote:
I have been using KDE/Plasma on openbsd since last week-end.
Amongst other bugs, mostly minor, which I should also report,
there is this one : when opening an new instance of konsole,
Plasma's
On Thu Jan 18, 2024 at 03:33:48PM +0100, Sylvain Saboua wrote:
> I have been using KDE/Plasma on openbsd since last week-end.
>
> Amongst other bugs, mostly minor, which I should also report,
> there is this one : when opening an new instance of konsole,
> Plasma's terminal emulator program, the
I have been using KDE/Plasma on openbsd since last week-end.
Amongst other bugs, mostly minor, which I should also report,
there is this one : when opening an new instance of konsole,
Plasma's terminal emulator program, the fallback folder location
will be in / instead of $HOME (in my case
On 21.06.23 18:27, Mikhail wrote:
Just installed latest amd64 install73.img from cdn.openbsd.org
OpenBSD 7.3-current (GENERIC.MP) #1253 Tue Jun 20 13:52:16 MDT 2023
and after installation it can't proceed further than
root on sd0a (..) swap on sdb0b dump on sd0b
Was working fine couple
> > and after installation it can't proceed further than
> >
> > root on sd0a (..) swap on sdb0b dump on sd0b
> >
> > Was working fine couple days ago.
> >
> > Is it known issue?
>
> Could you please share a dmesg of your system?
OpenBSD 7.3
Latest snapshot booted normally.
OpenBSD 7.3 GENERIC.MP#1254 amd64
On 6/21/23 12:27, Mikhail wrote:
Just installed latest amd64 install73.img from cdn.openbsd.org
OpenBSD 7.3-current (GENERIC.MP) #1253 Tue Jun 20 13:52:16 MDT 2023
and after installation it can't proceed further than
root
On Wed, Jun 21, 2023 at 07:27:44PM +0300, Mikhail wrote:
> Just installed latest amd64 install73.img from cdn.openbsd.org
>
> OpenBSD 7.3-current (GENERIC.MP) #1253 Tue Jun 20 13:52:16 MDT 2023
>
> and after installation it can't proceed further than
>
> root on sd0a (.
On Wed, Jun 21, 2023 at 04:40:59PM -0500, Scott Cheloha wrote:
> On Wed, Jun 21, 2023 at 01:03:03PM -0600, Chris Waddey wrote:
> > Sorry for breaking the thread, I wasn't subscribed to misc, but found
> > this in the archives.
> >
> > After some testing, it looks like the recent uvm_meter()
On Wed, Jun 21, 2023 at 11:25:27PM +0200, Claudio Jeker wrote:
> On Wed, Jun 21, 2023 at 01:03:03PM -0600, Chris Waddey wrote:
> > Sorry for breaking the thread, I wasn't subscribed to misc, but found
> > this in the archives.
> >
> > After some testing, it looks like the recent uvm_meter()
On Wed, Jun 21, 2023 at 01:03:03PM -0600, Chris Waddey wrote:
> Sorry for breaking the thread, I wasn't subscribed to misc, but found
> this in the archives.
>
> After some testing, it looks like the recent uvm_meter() commit is what
> did this (to my machine at least).
>
> The git commit for
bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.3 @ 0x439de000 (69 entries)
bios0: vendor LENOVO version "FHCN54WW" date 07/05/2021
bios0: LENOVO 82FG
efi0 at bios0: UEFI 2.7
efi0: INSYDE Corp. rev 0x59474054
acpi0 at bios0: ACPI 6.
Sorry for breaking the thread, I wasn't subscribed to misc, but found
this in the archives.
After some testing, it looks like the recent uvm_meter() commit is what
did this (to my machine at least).
The git commit for that is 71d823ace2523fb9fee2d1ab9b4d92a18d3f5714.
I compiled the commit right
and after installation it can't proceed further than
root on sd0a (..) swap on sdb0b dump on sd0b
Was working fine couple days ago.
Is it known issue?
OpenBSD 7.3-current (GENERIC.MP) #1253: Tue Jun 20 13:52:16 MDT 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real
Just installed latest amd64 install73.img from cdn.openbsd.org
OpenBSD 7.3-current (GENERIC.MP) #1253 Tue Jun 20 13:52:16 MDT 2023
and after installation it can't proceed further than
root on sd0a (..) swap on sdb0b dump on sd0b
Was working fine couple days ago.
Is it known issue?
forgot mailinglist in reply, everything works now and my apologies: can not
figure out how I missed this one alias for 3 days ...
Greetings
sarag
> Von: sarag
> Datum: 9. Juni 2023 um 13:30:38 MESZ
> An: Janne Johansson
> Betreff: Aw: tmux only possible as root and not as normal
-1000/{,default}}}
Cheers,
Paul 'WEiRD' de Weerd
On Fri, Jun 09, 2023 at 02:18:56AM +0200, Thomas Schnell wrote:
| Hi there,
|
| I have three new installed machines, that show the same strange behaviour:
tmux is only startable as root, if I want to start it with command "tmux" as
n
Den fre 9 juni 2023 kl 09:44 skrev sa...@sarag.net :
> Ah, sorry, forgot to mention that: no, neither root nor user have any
> config file, this is directly after fresh install, so system defaults
> should have been used…
>
> >> I have three new installed machines, that
Ah, sorry, forgot to mention that: no, neither root nor user have any config
file, this is directly after fresh install, so system defaults should have been
used…
greetings, sarag
> On 9. Jun 2023, at 07:10, Anton Konyahin wrote:
>
> On 09/06, Thomas Schnell wrote:
>> Hi
On 09/06, Thomas Schnell wrote:
Hi there,
I have three new installed machines, that show the same strange behaviour: tmux is only startable as root, if I want to
start it with command "tmux" as normal user (which is in wheel group, btw), I get the error "no
sessions"
Hi there,
I have three new installed machines, that show the same strange behaviour: tmux
is only startable as root, if I want to start it with command "tmux" as normal
user (which is in wheel group, btw), I get the error "no sessions", if I try to
start it with comman
the “From address” for when the daily o
>> utput reports are run. I want to use a real email address rather than the def
>> ault of Charlie Root “root@hostname”.
>>
>> I have tried to use a /root/.mailrc option and set the “from” address but thi
>> s seems to be ign
On Sat, 06 May 2023 10:03:45 +1000, Nino Sidoti wrote:
> I am trying to work out how to change the “From address” for when the daily o
> utput reports are run. I want to use a real email address rather than the def
> ault of Charlie Root “root@hostname”.
>
> I have tried to use
Am 06.05.2023 02:03 schrieb Nino Sidoti:
Hello,
I am trying to work out how to change the “From address” for when the
daily output reports are run. I want to use a real email address
rather than the default of Charlie Root “root@hostname”.
It takes the name from /etc/passwd. See vipw(8
Hello,
I am trying to work out how to change the “From address” for when the daily
output reports are run. I want to use a real email address rather than the
default of Charlie Root “root@hostname”.
I have tried to use a /root/.mailrc option and set the “from” address but this
seems
Janne: I will read those man pages. I have never read or used fbtab
or hotplugd. Thanks for the recommendations.
Stuart: Glad I'm not messing things up that much. Will remember
your advice of a dedicated user in case of a cli program.
Thank you,
On 2023-02-01, Leonardo Moreno wrote:
> Hello,
>
> I had trouble getting my Yubikey recognized by KeepassXC
> as a normal user (staff class, wheel group).
>
> I compared the ktrace of ykpersonalize between root and this user
> and saw that the latter couldn't access /dev/u
> and saw that the latter couldn't access /dev/usb0 and /dev/ugen1.00
> I modified the permissions and I can now use the Yubikey.
>
> My question is:
> Is this way of solving the problem correct in terms of security
> or best practices? If not, do you have any recommendations as how
> to do this
Hello,
I had trouble getting my Yubikey recognized by KeepassXC
as a normal user (staff class, wheel group).
I compared the ktrace of ykpersonalize between root and this user
and saw that the latter couldn't access /dev/usb0 and /dev/ugen1.00
I modified the permissions and I can now use
I have a basic web server set up
server "example.com" {
listen on * port 80
gzip-static
directory {
index index.html
no auto index
}
}
When opening the root webpage (http://example.com), the server does not
respond with "Content-Encoding: gzip&qu
On Wed, Aug 31, 2022 at 01:13:11PM +0100, li...@xza.fr wrote:
>
> SCANNING ON OPENBSD WITH SANE, AS NON-ROOT USER
>
> foreword: wanted to put this guide somewhere
>
>
> install sane:
>
> # pkg_add sane
>
>
> plug in the scanner, and immediately after, r
SCANNING ON OPENBSD WITH SANE, AS NON-ROOT USER
foreword: wanted to put this guide somewhere
install sane:
# pkg_add sane
plug in the scanner, and immediately after, run this command:
# dmesg | tail -20
ugen0 at uhub0 port 3 ""
the output should appear as above
now t
dev sbin
> >> .profilebsd.booted etc sys
> >> altroot bsd.rd hometmp
> >> auto_upgrade.conf bsd.sp mailwrapper.coreusr
> >> bin bsd.upgrade r
sys
>> altroot bsd.rd hometmp
>> auto_upgrade.conf bsd.sp mailwrapper.coreusr
>> bin bsd.upgrade rootvar
>> upgrade# df -h
>> Filesystem SizeUsed Avail Capac
simple. I've read through the upgrade
documentation, and tried to google my problem but I could not fix
my problem.
I upgrade with sysupgrade. After boot I try to select root disk:
Available disks are: .
Which disk is the root disk? ('?' for details) ?
sd0: NVMe, Samsung SSD 970, 2B2Q (232.9G
ot bsd.rd hometmp
> auto_upgrade.conf bsd.sp mailwrapper.coreusr
> bin bsd.upgrade rootvar
> upgrade# df -h
> Filesystem SizeUsed Avail Capacity Mounted on
> /dev/rd0a 3.5M3.0M451
bsd.rd hometmp
auto_upgrade.conf bsd.sp mailwrapper.coreusr
bin bsd.upgrade rootvar
upgrade# df -h
Filesystem SizeUsed Avail Capacity Mounted on
/dev/rd0a 3.5M3.0M451K
On 2022-04-21, michal.lyszc...@bofc.pl wrote:
>> 16 partitions:
>> #size offset fstype [fsize bsize cpg]
>> a: 8400960 1024 4.2BSD 2048 16384 12960
>> b: 67119581 8401984swap
>> c:4883971680
, and tried to google my problem but I could not fix
my problem.
I upgrade with sysupgrade. After boot I try to select root disk:
> Available disks are: .
> Which disk is the root disk? ('?' for details) ?
> sd0: NVMe, Samsung SSD 970, 2B2Q (232.9G)
> Available disks are: .
> Which disk i
for the
correct root device.
On amd64, hppa, etc, you can pass parameters to the bootloader via
/etc/boot.conf on the boot device but it doesn't look like that option exists
on alpha. I did some checking but was wondering if there was a more permanent
solution to this configuration problem (besides
Hello,
I just installed an amd64 snapshot and spotted 2 odd things. I see there is
a mail for root, but when i run mail command i get the text No mail for
root.
The other is I login in xenodm to use cwm for the fisrt time after install
and the xenodm is restarted. Second login and future logins
On Sun, Jan 31, 2021 at 12:06:37PM +0100, Stefan Sperling wrote:
On Sun, Jan 31, 2021 at 11:47:04AM +0100, Stefan Sperling wrote:
In general, crypto softraid volumes don't auto-assemble.
I forgot that softraid volumes that use a key disk instead of a
passphrase will auto-assemble. Have you
On Wed, Feb 10, 2021 at 03:59:12PM +0100, Stefan Sperling wrote:
On Wed, Feb 10, 2021 at 01:00:33PM +, Frank Beuth wrote:
On Tue, Feb 02, 2021 at 10:50:39PM +0100, Stefan Sperling wrote:
> The idea of protecting key disks with a passphrase (two-factor auth) has
> been raised before. It has
On Thu, Feb 11, 2021 at 06:56:40PM +, tetrahe...@danwin1210.me wrote:
> On Sun, Jan 31, 2021 at 12:06:37PM +0100, Stefan Sperling wrote:
> > On Sun, Jan 31, 2021 at 11:47:04AM +0100, Stefan Sperling wrote:
> > > In general, crypto softraid volumes don't auto-assemble.
> >
> > I forgot that
On Wed, Feb 10, 2021 at 01:00:33PM +, Frank Beuth wrote:
> On Tue, Feb 02, 2021 at 10:50:39PM +0100, Stefan Sperling wrote:
> > The idea of protecting key disks with a passphrase (two-factor auth) has
> > been raised before. It has not been implemented yet, simply because nobody
> > has done
On Tue, Feb 02, 2021 at 10:50:39PM +0100, Stefan Sperling wrote:
The idea of protecting key disks with a passphrase (two-factor auth) has
been raised before. It has not been implemented yet, simply because nobody
has done the work. A search of the mailing list archives should yield
some prior
On Tue, Feb 02, 2021 at 07:04:38AM +, tetrahe...@danwin1210.me wrote:
> Looking thru the manpages, I don't see any provision for adding AND / OR
> logic to keys (e.g require both passphrase AND keydisk to boot, require
> passphrase OR keydisk, etc) the way Linux cryptsetup provides, at least,
On Sun, Jan 31, 2021 at 12:06:37PM +0100, Stefan Sperling wrote:
On Sun, Jan 31, 2021 at 11:47:04AM +0100, Stefan Sperling wrote:
In general, crypto softraid volumes don't auto-assemble.
I forgot that softraid volumes that use a key disk instead of a
passphrase will auto-assemble. Have you
On Sun, Jan 31, 2021 at 11:47:04AM +0100, Stefan Sperling wrote:
> In general, crypto softraid volumes don't auto-assemble.
I forgot that softraid volumes that use a key disk instead of a
passphrase will auto-assemble. Have you already tried that?
A disklabel slice on the USB key could act as a
ks for available volumes
> during the boot sequence?
>
> Why would the kernel, when booted from a bootloader on one physical disk, be
> able to find a root device -- but, when booted from a bootloader on a
> different physical disk, not be able to do so? (even when the bootloader
,
installboot manpages (as far as I can tell) offer no answers.
Does anyone here understand how the kernel looks for available volumes
during the boot sequence?
Why would the kernel, when booted from a bootloader on one physical
disk, be able to find a root device -- but, when booted from
On Tue, Jan 26, 2021 at 03:41:23PM +, tetrahe...@danwin1210.me wrote:
Any ideas why the kernel isn't seeing sr0a as a root device?
As suggested in the "Managed to mess up the system encrypted disk. I can
no longer boot" thread, I tried running installboot from the working
(b
: if you have your bootloader with you at all times in
your pocket, an evil maid can't tamper with it to recover your FDE
encryption key.
I managed to get the thing not to panic by using
the -a flag, i.e
boot> boot sr0a:/bsd -a
Unfortunately, when I use the kernel-suggested default devices (r
On Jan 23 23:04:54, tetrahe...@danwin1210.me wrote:
> If I boot from the standard bootloader on the FDE encrypted disk itself,
> everything boots fine.
Great.
> I am trying to set up the bootloader on an external
> USB stick to boot my FDE-encrypted disk:
Why? You say you can boot from the disk
oot sr0a:/bsd
When booting, the boot stops immediately after "scsibus4 at softraid0:
256 targets" with the error message "panic: root device (..) not found"
If I boot from the standard bootloader on the FDE encrypted disk itself,
everything boots fine.
Has something ch
On 2020-03-21, putridsou...@gmail.com wrote:
> I'm have never tried the ports system before.
> I have read through the faq and the man pages,
> but I get stuck at building dependencies.
> I follow through the fetch,checksum steps and then
> for 'make prepare' as local user,
> I'm greeted with
nc-3.1.3.tgz
> ===> Cleaning for rsync-3.1.3
> ===> Verifying specs: c
> ===> found c.95.1
> ===> Installing rsync-3.1.3 from /usr/ports/packages/amd64/all/
> pkg_add: pkg_add must be run as root
> *** Error 1 in /usr/ports/net/rsync
> (/usr/ports/infrastructure/m
from /usr/ports/packages/amd64/all/
pkg_add: pkg_add must be run as root
*** Error 1 in /usr/ports/net/rsync
(/usr/ports/infrastructure/mk/bsd.port.mk:2028
'/var/db/pkg/rsync-3.1.3/+CONTENTS': @/usr/bin/env -i PKG...)
*** Error 1 in /usr/ports/net/rsync
(/usr/ports/infrastructure/mk/bsd.port.m
I have need to call sysctl() in a C program to read
“sysctl kern.version”. Will there be a pledge() to prohibit further calls
to sysctl()? I’m kinda afraid that putting a sysctl call could conceivably
leave it vulnerable to calling it again in the case the mitigations fail
and sysctl() is run to
ce RET ktrace 0
>> > 58118 ktrace CALL
>> execve(0x7f7d9100,0x7f7d9710,0x7f7d9730)
>> > 58118 ktrace NAMI "*/usr/local/heimdal/bin/su*"
>> > 58118 ktrace ARGS
>> > [0] = "su"
>> > [1] = &quo
; 58118 ktrace NAMI "*/usr/local/heimdal/bin/su*"
> > 58118 ktrace ARGS
> > [0] = "su"
> > [1] = "-"
> > [2] = "root"
> > ORLOV-NB$ whereis su
> > /usr/bin/su
>
> whereis isn't terribly
[0] = "su"
> [1] = "-"
> [2] = "root"
> ORLOV-NB$ whereis su
> /usr/bin/su
whereis isn't terribly useful, it doesn't use $PATH, instead uses a
fixed path of common directories.
The "type" builtin in most Bourne-style shells is usually more helpful.
Lol!
ORLOV-NB$ kdump -f ktrace.out
58118 ktrace RET ktrace 0
58118 ktrace CALL execve(0x7f7d9100,0x7f7d9710,0x7f7d9730)
58118 ktrace NAMI "*/usr/local/heimdal/bin/su*"
58118 ktrace ARGS
[0] = "su"
[1] = "-"
[2] = &q
did it happen?
> >>
> >> OpenBSD 6.5 current
> >> $su - root
> >> root's password:
> >> Segmentation fault
> >> $ doas su - root
> >> #
> >>
> >> --
> >> Dmitry Orlov
> > what current? What arch?
> >
&
On 31.07.19 17:00, Solene Rapenne wrote:
On Wed, Jul 31, 2019 at 04:49:54PM +0500, dmitry.sensei wrote:
Hi!
why did it happen?
OpenBSD 6.5 current
$su - root
root's password:
Segmentation fault
$ doas su - root
#
--
Dmitry Orlov
what current? What arch?
works for me©
OpenBSD 6.5-current
On Wed, Jul 31, 2019 at 04:49:54PM +0500, dmitry.sensei wrote:
> Hi!
> why did it happen?
>
> OpenBSD 6.5 current
> $su - root
> root's password:
> Segmentation fault
> $ doas su - root
> #
>
> --
> Dmitry Orlov
what current? What arch?
works for me©
OpenBS
Hi!
why did it happen?
OpenBSD 6.5 current
$su - root
root's password:
Segmentation fault
$ doas su - root
#
--
Dmitry Orlov
Ingo Schwarze wrote:
> su(I) goes back all the way to v1: (...) It wasn't in v0 PDP-7 UNIX though:
> https://www.tuhs.org/Archive/Distributions/Research/McIlroy_v0/UnixEditionZero.txt
>From that text file's Introduction:
>> Besides the system proper, the major programs available under
>> UNIX
Ingo Schwarze wrote:
> su(I) goes back all the way to v1: (...) It wasn't in v0 PDP-7 UNIX though:
> https://www.tuhs.org/Archive/Distributions/Research/McIlroy_v0/UnixEditionZero.txt
>From that text file:
>> 8.4 chdir -- change directories
>>
>> To change the current directory, use
>>
>>
On 13/06/2019 20:56, Misc User wrote:
> On 6/13/2019 9:42 AM, Adam Thompson wrote:
>> On 2019-06-12 03:55, Ingo Schwarze wrote:
>> During initial system installation & deployment, before doas is
>> configured, and assuming you haven't [yet] added your SSH keys to
>>
On 6/13/2019 9:42 AM, Adam Thompson wrote:
On 2019-06-12 03:55, Ingo Schwarze wrote:
During initial system installation & deployment, before doas is
configured, and assuming you haven't [yet] added your SSH keys to
~root/.ssh/allowed_keys, it's quite impossible to avoid using su.
(A
Well, I often need a root shell.
Usually I login as a user in group wheel, but not operator!
The perils of group operator were explained in a previous thread.
I don't use that group anymore.
As I understand, nothing like a web browser, etc. should ever be used by
root. So I don't.
I have been
On 2019-06-12 03:55, Ingo Schwarze wrote:
Even though su(1) can still be used today to relinquish privilege
when you are already root, no more development is done on it and people
rarely look at the manual page. The last time new functionality was
added to the su(1) manual page was almost
.113 Jun 2019 12:59:51 - 1.33
@@ -273,7 +273,7 @@
.Sh HISTORY
A
.Nm
-command appeared in
-.At v7 .
+command first appeared in
+.At v1 .
.Sh BUGS
The login name is not optional for root if there are shell arguments.
On 2019-06-13, "Theo de Raadt" wrote:
>> I always considered that su is coming from _s_uper _u_ser. But maybe I
>> am wrong, I am not from old UNIX days.
>
> incorrect.
>
> NAME
> su - substitute user identity
Well, that's V7, which appears to have engaged in a bit of revisionism
together
> Ingo seems to be rather good at those.
My favorites are Nick Holland's answers. But let's not forget Stuart
Henderson, Henning Brauer, Stefan Sperling, Marc Espie ... and Dr.
House. The answers from the latter are hard to digest but always solid
and in place. May be others too, my excuses for
Nan Xiao writes:
> Hi Ingo,
>
> Thanks for your detailed explanation!
Ingo seems to be rather good at those. The last trivial question I asked
got an exposé on precisely how the ports and base development processes
interact with one another.
I propose a motion that every answer Igno makes to a
On Thu, Jun 13, 2019 at 08:55:09AM +0100, Andrew Luke Nesbit wrote:
> On 13/06/2019 07:17, Theo de Raadt wrote:
> > Mihai Popescu wrote:
> >
> >>> ... if no account is provided, root is the default
> >>
> >> I always considered that su is coming from
On 13/06/2019 07:17, Theo de Raadt wrote:
> Mihai Popescu wrote:
>
>>> ... if no account is provided, root is the default
>>
>> I always considered that su is coming from _s_uper _u_ser. But maybe I
>> am wrong, I am not from old UNIX days.
>
> incorrect
words
> > which said if no account is provided, root is the default.
>
> The BUGS section says so indirectly, but i agree that is not sufficient.
> A manual page ought to explain the behaviour of a utility explicitly
> and in the DESCRIPTION section. All the more so for aspects as
Mihai Popescu wrote:
> > ... if no account is provided, root is the default
>
> I always considered that su is coming from _s_uper _u_ser. But maybe I
> am wrong, I am not from old UNIX days.
incorrect.
NAME
su - substitute user identity
> ... if no account is provided, root is the default
I always considered that su is coming from _s_uper _u_ser. But maybe I
am wrong, I am not from old UNIX days.
Hello Nan Xiao,
Nan Xiao wrote on Wed, Jun 12, 2019 at 02:19:08PM +0800:
> I read su manual (https://man.openbsd.org/su.1), but can't find words
> which said if no account is provided, root is the default.
The BUGS section says so indirectly, but i agree that is not sufficient.
A manua
Hi misc@,
Greeting from me!
I read su manual (https://man.openbsd.org/su.1), but can't find words
which said if no account is provided, root is the default. But for
doas(https://man.openbsd.org/doas.1), it has following words:
-u userExecute the command as user. The default is root.
I am
On Wed, Mar 20, 2019 at 08:38:18PM +1300, worik wrote:
> Yes.
>
> But is the error message:
>
> httpd: need root privileges
>
> Accurate?
This is the paradox of modern secure code.
You need to start stuff as root because you want to do stuff in startup
code that yo
gt; as a user to serve some files and I found this error:
> >> httpd: need root privileges
> >>
> >> I would think there would be value in letting httpd be run
> >> by standard users.
> > For security reasons, you absolutely do *not* want that.
> >
>
On 20/03/19 3:01 AM, Ingo Schwarze wrote:
> Hi Alfred,
>
> Alfred Morgan wrote on Tue, Mar 19, 2019 at 08:05:33AM -0500:
>
>> I tried starting a temporary httpd server on port 8080
>> as a user to serve some files and I found this error:
>> httpd: need root
Listen to ingo's advice, just put the stuff in a dir in /var/www/
On March 19, 2019 2:05:33 PM GMT+01:00, Alfred Morgan wrote:
>I tried starting a temporary httpd server on port 8080 as a user to
>serve
>some files and I found this error:
>httpd: need root privileges
>
>I would
Hi Alfred,
Alfred Morgan wrote on Tue, Mar 19, 2019 at 08:05:33AM -0500:
> I tried starting a temporary httpd server on port 8080
> as a user to serve some files and I found this error:
> httpd: need root privileges
>
> I would think there would be value in letting httpd be ru
I tried starting a temporary httpd server on port 8080 as a user to serve
some files and I found this error:
httpd: need root privileges
I would think there would be value in letting httpd be run by standard
users.
--
-alfred
rade the Unifi Controller net/unifi/stable (version 5.8.30) from
> > >> ports.
> > >> The controller service doesn??t start wit rcctl(8) but works fine when
> > >> running as root.
> > >> My guess is that _unifi is not allowed to start monogd but don??t have
s.
> >> The controller service doesn??t start wit rcctl(8) but works fine when
> >> running as root.
> >> My guess is that _unifi is not allowed to start monogd but don??t have
a
> >> clue how to fix this...
> >> Does it matter if databases/mongo is instal
On 2019-01-08, Bryan Vyhmeister wrote:
> On Tue, Jan 08, 2019 at 03:27:39PM +0100, Thomas Huber wrote:
>> just upgrade the Unifi Controller net/unifi/stable (version 5.8.30) from
>> ports.
>> The controller service doesn??t start wit rcctl(8) but works fine when
>> r
On Tue, Jan 08, 2019 at 03:27:39PM +0100, Thomas Huber wrote:
> just upgrade the Unifi Controller net/unifi/stable (version 5.8.30) from
> ports.
> The controller service doesn??t start wit rcctl(8) but works fine when
> running as root.
> My guess is that _unifi is not allowed
Hi,
just upgrade the Unifi Controller net/unifi/stable (version 5.8.30) from
ports.
The controller service doesn´t start wit rcctl(8) but works fine when
running as root.
My guess is that _unifi is not allowed to start monogd but don´t have a
clue how to fix this...
Does it matter if databases
e and tried to create an image of the drive, but it
> fails
>
> 20190102-1435:root@curry:/root:#time dd if=/dev/rsd2c of=/root/corsair.iso
> bs=1k
> dd: /dev/rsd2c: Input/output error
> 15958016+0 records in
> 15958016+0 records out
> 16341008384 bytes transferred in 7313.789 sec
having some permission issues mounting a usb drive, as root.
I have
been able to mount other usb drives just fine. (Also tried with the
12/29 snapshots as well, same issue)
#disklabel sd4
...
# size offset fstype [fsize bsize cpg]
a:
On 1/1/19 11:53 PM, Otto Moerbeek wrote:
On Tue, Jan 01, 2019 at 07:25:14PM -0700, myml...@gmx.com wrote:
I just did a new install of current AMD64 from the 12/31/2018 snapshot and
having some permission issues mounting a usb drive, as root. I have been
able to mount other usb drives just
a usb drive, as root.
I have
been able to mount other usb drives just fine. (Also tried with the
12/29 snapshots as well, same issue)
#disklabel sd4
...
# size offset fstype [fsize bsize cpg]
a: 249682144 64 4.2BSD 2048
1 - 100 of 844 matches
Mail list logo
