Hi!
On one(out of two!) of my APUs sysupgrade fails, and I'm having trouble
understanding why.
This is what happens:
Available disks are: sd0.
Which disk is the root disk? ('?' for details) [sd0] sd0
Checking root filesystem (fsck -fp /dev/sd0a)... OK.
Mounting root filesystem (mount -o ro
On Sun, 5 Jan 2020 14:47:15 +0100
"lu hu" wrote:
> Hello,
>
> http://man.openbsd.org/sshd_config#PermitRootLogin
> says
> ...The default is prohibit-password.
> If this option is set to prohibit-password (or its deprecated alias,
> without-password), password and keyboard-interactive
Thanks all for the answers.
jca pointed out:
"OpenBSD doesn't support "POSIX" ACLs or extended attributes so DC
support is a pain (eg sysvol shares, etc)."
Code wasn't stripped from source, but need work to be enabled at least
with trivial database (tdb) to support ACLs/xattr.
After that, see
On Sun, Jan 5, 2020 at 1:05 PM Christer Solskogen
wrote:
>
> Sorry, I forgot to telll you that I run current. I was upgrading a snapshot
> from 1st of january to the latest one. But this has happened before (It
> looks like the last time sysupgrade did successfully work was 4th of
> December)
>
>
On 2020/01/05 07:43, Nazar Zhuk wrote:
> On 2020-01-04 09:21, Stuart Henderson wrote:
> > On 2020-01-04, Nazar Zhuk wrote:
> > > I get SCRIPT_FILENAME passed from httpd relative to httpd chroot
> > > (/site1/htdocs/... ) and PHP being chrooted into /var/www/site1 needs
> > > that to be relative
fuck I did a typo, sorry, I wanted to write:
66# sshd -T|grep -i permitr
permitrootlogin without-password
66#
really sorry.
But the issue is still there. man page says there should be prohibit-password
and not without-password
> Sent: Sunday, January 05, 2020 at 3:07 PM
> From: "lu hu"
>
On Sun, Jan 5, 2020 at 1:11 PM Anders Andersson wrote:
>
>
> Not sure if it's in any way related when it comes to doing a
> sysupgrade compared to a clean install, but did you see this thread
> and the corresponding BIOS upgrade?
>
>
Hello,
any thoughts anyone?
> Sent: Sunday, December 29, 2019 at 6:07 PM
> From: "lu hu"
> To: misc@openbsd.org
> Subject: Re: Why isn't ChallengeResponseAuthentication NO in sshd_config?
>
> Hello:
>
> 66# grep -i challenge /etc/ssh/sshd_config
> #ChallengeResponseAuthentication yes
> 66#
yes!
> Sent: Sunday, January 05, 2020 at 3:00 PM
> From: "Robert Klein"
> To: misc@openbsd.org
> Subject: Re: sshd_config#PermitRootLogin typo
>
> On Sun, 5 Jan 2020 14:47:15 +0100
> "lu hu" wrote:
>
> > Hello,
> >
> > http://man.openbsd.org/sshd_config#PermitRootLogin
> > says
> > ...The
Sorry, I forgot to telll you that I run current. I was upgrading a snapshot
from 1st of january to the latest one. But this has happened before (It
looks like the last time sysupgrade did successfully work was 4th of
December)
On Sun, Jan 5, 2020 at 12:58 PM Christer Solskogen <
who can bring up openiked.org to life?
> Sent: Tuesday, December 31, 2019 at 4:14 PM
> From: "Umgeher Torgersen"
> To: misc@openbsd.org
> Subject: Re: openiked.org down?
>
> yeah, it's down...
>
> ; <<>> DiG 9.4.2-P2 <<>> openiked.org
> ;; global options: printcmd
> ;; Got answer:
> ;;
On Thu, Oct 31, 2019 at 08:01:25AM -, Stuart Henderson wrote:
> On 2019-10-30, Jurjen Oskam wrote:
> >
> > All snapshots I tried up to and including this point did not show the
> > problem:
> > OpenBSD 6.6-beta (GENERIC.MP) #202: Mon Aug 12 11:01:21 MDT 2019
> >
> > All snapshots I tried
Stuart Henderson writes:
> On 2020/01/05 00:33, go...@disroot.org wrote:
> > January 5, 2020 2:24 AM, "Roderick" wrote:
> >
> > > On Sun, 5 Jan 2020, go...@disroot.org wrote:
> > >
> > >> so I don't understand what's wrong with FreeBSD and OpenBSD.
> > >
> > > I do not see a problem in CVS.
>
Hello,
http://man.openbsd.org/sshd_config#PermitRootLogin
says
...The default is prohibit-password.
If this option is set to prohibit-password (or its deprecated alias,
without-password), password and keyboard-interactive authentication are
disabled for root.
SO:
if I remove the
Read release(8), then write a script runs through the described process.
--
Morten Gade Liebach ★ https://m.lieba.ch/
‐‐‐ Original Message ‐‐‐
On Sunday, January 5, 2020 5:29 PM, Paul Suh wrote:
> Folks,
>
> My DuckDuckGo-fu seems to be weak right now.
>
> Is there a set of automated
On Sun, 5 Jan 2020 15:22:46 +0100
"lu hu" wrote:
> fuck I did a typo, sorry, I wanted to write:
>
> 66# sshd -T|grep -i permitr
> permitrootlogin without-password
> 66#
>
> really sorry.
>
> But the issue is still there. man page says there should be
> prohibit-password and not
HyperThread must be off! Danger!
Probably shouldn't enable virtualization unless using it.
Secure boot is off, that is correct.
Do you have the latest BIOS?
Will the disk boot if you skip UEFI completely and run in legacy mode?
Are you dual-booting with Windows? It hates everything and can mess
On Sun, Jan 05, 2020 at 06:08:55PM +, Paul Suh wrote:
> On Jan 5, 2020, at 12:43 PM, Morten Gade Liebach wrote:
> >
> > Read release(8), then write a script runs through the described process.
>
> I can do that, and will if I have to, but if someone has already done it or
> has a base to
Hi,
Recently I tried to use mu4e on OpenBSD. However the indexing
performance is dreadly slow compared to my Linux box. There was also an
issue report on mu upstream[1] where someone reported mu can only
process ~7msg/s on OpenBSD. I suspect it's because of the slow write
performance on FFS,
On 2020-01-03, jrmu wrote:
> inet 0.0.0.0 255.255.255.255 NONE \
> pppoedev cpsw0 authproto pap \
> authname '12345...@isp.net' authkey 'abcd1234' up
> dest 0.0.0.1
> #inet6 eui64
> !/sbin/route add default -ifp pppoe0 0.0.0.1
> #!/sbin/route add -inet6 default -ifp pppoe0 fe80::%pppoe0
I had
summary: OpenBSD installs to internal HDD from external USB but fails
to load after the first reboot. If the HDD is removed from the internal
port and is connected via a "SATA to USB" cable it boots succesfully.
I am a new and inexperienced user, excuse my ignorance.
All the details and things
Folks,
My DuckDuckGo-fu seems to be weak right now.
Is there a set of automated scripts somewhere that:
1) Checks anoncvs*.*.openbsd.org:/cvs for updates to the patch branch source
tree
2) Checks them out
3) Builds them
4) Builds a release
Then notifies me when this has happened?
I’m
On Sat, Jan 4, 2020 at 8:48 PM Theo de Raadt wrote:
>
SNIP
> wow this is going downhill. random solo-repo people telling us what to do
> when Chuck Cranor and I started this whole export-the-repo model.
>
> get some perspective dude, hopefully in the jungle.
It seems like a lot of people in
On Jan 5, 2020, at 12:43 PM, Morten Gade Liebach wrote:
>
> Read release(8), then write a script runs through the described process.
I can do that, and will if I have to, but if someone has already done it or has
a base to start from that would be better. (I’ve been building OpenBSD releases
Aham Brahmasmi wrote:
>If I am not wrong, the verification should fail.
If you have a system that uses private / public signing keys then, yes,
you're correct.
But:
1) In my opinion it's probably overkill for just doing backups. As I said
in my previous email, just using symmetric encryption
25 matches
Mail list logo
