Sebastien Marie wrote:
>
> I would recommand to run neofetch (or others fortune(6)-like program) under
> interactive shell only.
>
While this is good advice, security(8) cannot guarantee that .profile will not
generate output to stdout or stderr, and the code makes this assumption, so the
output
>Synopsis: security(8) throws false error
>Category: security(8)
>Environment:
System : OpenBSD 7.6
Details : OpenBSD 7.6-current (CUSTOM) #4: Sat Dec 14 01:13:27 GMT
2024
lloyd@bsdtst01:/sys/arch/amd64/compi
>Synopsis: login_yubikey(8) leaks sensitive data to syslog
>Category: Security
>Environment:
System : OpenBSD 7.6
Details : OpenBSD 7.6-current (CUSTOM) #4: Sat Dec 14 01:13:27 GMT
2024
lloyd@bsdtst01:/sys/arch/amd64/compi
or this to work properly.
My hope is that as the wg protocol matures, this be considered a feature
enhancement whereby you can place a maximum aged handshake into the .conf
file, after which it will give up shouting into the void, rather then
resorting to ugly hacks such as the script mentioned above.
Appreciate the extended discussion on this.
Regards
Lloyd
However I believe it makes the assumption
that
the mobile device would continue to roam for eternity, and never be switched
off.
Regards
Lloyd
>Synopsis: Inactive Wireguard connections never time out
>Category: Networking
>Environment:
System : OpenBSD 7.6
Details : OpenBSD 7.6-current (CUSTOM) #4: Sat Dec 14 01:13:27 GMT
2024
lloyd@bsdtst01:/sys/arch/amd64/compi
Ingo Schwarze wrote:
> The problem only occurs when the initialization file starts a background
> process that prints to standard output, which is even more crazy.
The example given was a foreground process.
> Normal output generated by the initialization file occurs before
> the "echo ENV", so
Honestly this is probably a corner case but in any circumstance the
output of stdout should not be trusted Thanks for the commit.
Regards
Lloyd
Stuart Henderson wrote:
>
> > Running neofetch, fortune, etc. tools from .profile is not uncommon.
>
> for root? really?
Under Linux, neofetch is typically run from /etc/profile.d/ which executes
for all users by default (including root). I'll reserve comment as to
whether this is a good idea or
> Are you tight on space in /usr? That could be one reason (i.e. wasn't
> enough space to fully unpack).
FWIW I've had kernel reordering break on systems with modestly-sized disks
(think a VM with 16GB storage). Accepting defaults from the auto-partitioner
will happily create an undersized /usr wh
>Synopsis: reorder_kernel generates corrupted /bsd when /usr is full
>Category: system
>Environment:
System : OpenBSD 7.7
Details : OpenBSD 7.7 (GENERIC) #619: Sun Apr 13 08:19:34 MDT 2025
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64
Does the EdgeRouter hw lack an onboard real-time clock?
If so it probably defaults to kernel build time if it has no reference
until it contacts NTP.
Kirill A. Korinsky wrote:
> On Mon, 12 May 2025 11:40:48 +0200,
> Kirill A. Korinsky kir...@korins.ky wrote:
>
> > > Synopsis: octeon port doesn'
ystem, etc.)
Lloyd wrote:
> > Synopsis: reorder_kernel generates corrupted /bsd when /usr is full
> > Category: system
> > Environment:
>
> System : OpenBSD 7.7
> Details : OpenBSD 7.7 (GENERIC) #619: Sun Apr 13 08:19:34 MDT 2025
> dera...@amd64.openbsd.org:/usr
If it's a problem, and it takes last modified time for /,
consider creating /etc/rc.shutdown to touch a file in /
Kirill A. Korinsky wrote:
> On Mon, 12 May 2025 19:42:47 +0200,
> Crystal Kolipe kolip...@exoticsilicon.com wrote:
>
> > On Mon, May 12, 2025 at 05:03:59P
>Synopsis: smtpd does not reject -bs switch causing deadlock
>Category: mail
>Environment:
System : OpenBSD 7.7
Details : OpenBSD 7.7 (GENERIC) #619: Sun Apr 13 08:19:34 MDT 2025
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/G
Jonathan Matthew wrote:
> lld has a --no-mmap-output-file option that causes it to use plain write(2)
> calls to generate the output file. Perhaps it'd be worth using that for
> kernel linking and other stuff we relink at boot time?
This actually worked:
$ cat relink.log
(SHA256)
Jonathan Matthew wrote:
> On Thu, May 15, 2025 at 12:05:25PM +0200, Mark Kettenis wrote:
>
> > > Date: Thu, 15 May 2025 11:22:17 +0200
> > > From: Claudio Jeker cje...@diehard.n-r-g.com
> > >
> > > On Thu, May 15, 2025 at 06:28:42PM +1000, Jonathan Matthew wrote:
> > >
> > > > On Tue, May 13, 2
nually (making no changes) and it completed without error.
Lloyd wrote:
> Did a fix ever get merged for this?
>
> I tested enough to validate passing --no-mmap-output-file does indeed
> fix the pesky broken-kernel-upon-ENOSPC problem, not sure of any
> ancillary impacts.
>
>
Did a fix ever get merged for this?
I tested enough to validate passing --no-mmap-output-file does indeed
fix the pesky broken-kernel-upon-ENOSPC problem, not sure of any
ancillary impacts.
On Wednesday, May 21st, 2025, Jonathan Matthew wrote:
> On Thu, May 15, 2025 at 12:05:25PM +0200, Mark Ket
ing and there is some more data beyond "wget" in the
exploit (including a URL and more shell commands) which was truncated from the
relayd log as well. Obviously this is targeting some other type of device but
something is not right here because there should be consistency between httpd
and relayd.
Probably not a bad idea to run this through a fuzzer.
Regards
Lloyd
20 matches
Mail list logo
