On Tue, Apr 07, 2020, Vitaliy Makkoveev wrote:
> send mail via yahoo's smtps. Error is "SSL failed: error:1404B3F2:SSL
> routines:ST_CONNECT:sslv3 alert unexpected message". mutt on this machine
> set smtp_url = 'smtps://lo...@smtp.mail.yahoo.com:465/'
Try to reproduce the problem using the
On Sat, Apr 4, 2020 at 1:14 AM Justin Noor wrote:
>
> Hello OpenBSD Community,
>
Hi!
> [SNIP]
> had no data on them, other than the FreeBSD installation sets, I decided
> not to clean the boot code area with 'dd if=/dev/zero of=/dev/rsd0c bs=1
> count=1'.
>
>
That clears one byte. You may
On Mon, Apr 06, 2020 at 02:23:20PM +0200, Riccardo Mottola wrote:
> Hi Marcus,
>
> Marcus MERIGHI wrote:
> > Hello Riccardo,
> >
> > startx(1) had it's setuid bit removed. I think in the timeframe you are
> > upgrading over. The canonical advice is to use xenodm(1).
> >
> > Marcus
> >
>
>
Hi,
For a long time, the /boot and pxeboot of i386 would boot amd64's
kernel and amd64's would boot i386's kernel.
My tftp server had both amd64 and i386 bsd.rd files named
"bsdamd64.rd" and "bsdi386.rd", snapshots downloaded daily. But
recently, I discovered I could not PXE boot i386's bsd.rd
After upgrading from 3 days old snapshot to 6.7-beta snapshot mutt can't
send mail via yahoo's smtps. Error is "SSL failed: error:1404B3F2:SSL
routines:ST_CONNECT:sslv3 alert unexpected message". mutt on this machine
restored from backup to old snapshot works fine.
.muttrc contains:
cut
Hello again,
I do not have a recent dmesg, but here is one from before the incident:
OpenBSD 6.6-current (GENERIC.MP) #401: Sat Oct 26 19:43:34 MDT 2019
My ThinkPad is actually running OpenBSD 6.6-current (GENERIC.MP) #107
from yesterday Apr 05
>
Hi all,
After a discussion at work, I started looking at enabling confirmation
before authentication through ssh-agent by default. When logging in
through xdm, the default Xsession runs `ssh-add < /dev/null` (see line
36 in /etc/X11/xdm/Xsession). My keys are loaded and I can log in to
remote
On 2020-04-01, Stephan Mending wrote:
> I've been experiencing issues upgrading my -current machines to the
> next snapshots by upgrading via `sysupgrade -ns`.
Feeding out to some mirrors isn't going great at the moment so it's
likely to be a bit intermittent.
Hello,
I have been using OpenBSD snapshots since autumn 2018 on a ThinkPad
X200. My machine is librebooted and apart from the well-known
framebuffer issue during boot, everything works fine.
A couple of weeks ago i accidentally spilled a glass of red wine over
the keyboard. I opened the machine
Hi Marcus,
Marcus MERIGHI wrote:
> Hello Riccardo,
>
> startx(1) had it's setuid bit removed. I think in the timeframe you are
> upgrading over. The canonical advice is to use xenodm(1).
>
> Marcus
>
exactly, that was it... the error message wasn't that helpful.
xenodm works.. but since I
Hello Riccardo,
startx(1) had it's setuid bit removed. I think in the timeframe you are
upgrading over. The canonical advice is to use xenodm(1).
Marcus
riccardo.mott...@libero.it (Riccardo Mottola), 2020.04.06 (Mon) 11:57 (CEST):
> Hi,
>
> lockdown times gave me finally times to update my
Hi,
lockdown times gave me finally times to update my workstation/home
server to 6.6 too, after my successful laptop upgrades.
I was a moment scared when fw_update told me to reboot due to microcode
update :-P But it went fine.
I followed 6.5 -> 6.6 upgrade. All packages are upgraded too
On Sat, Apr 04, 2020 at 08:22:27PM +0200, Marko Cupać wrote:
> On 2020-03-31 10:07, Marko Cupać wrote:
> > On Mon, 30 Mar 2020 14:33:46 +0300
> > Vitaliy Makkoveev wrote:
> >
> > > On Mon, Mar 30, 2020 at 02:28:08PM +0300, Vitaliy Makkoveev wrote:
> > > > You have pipex(4) disabled. Is it still
13 matches
Mail list logo
