Re: Compilations errors with plan9port on 2018/04/05 snapshot

[Philip Guenther]

On Thu, Apr 5, 2018 at 9:50 PM, Philip Guenther  wrote:

> On Thu, Apr 5, 2018 at 7:53 PM, Patrick Marchand  > wrote:
>
>> Output of compiling plan9port on amd64 with the april 5 snaphot
>>
> ...
>
>> ===>  Patching for plan9port-20180117
>> Segmentation fault (core dumped)
>> *** Warning in /usr/ports/plan9/plan9port: "uname -m" returned non-zero
>>
>
> dmesg from this box, please.
>

Also, does this segfault happen consistently at that same exact spot, or is
it inconsistent?

Re: Compilations errors with plan9port on 2018/04/05 snapshot

[Philip Guenther]

On Thu, Apr 5, 2018 at 7:53 PM, Patrick Marchand 
wrote:

> Output of compiling plan9port on amd64 with the april 5 snaphot
>
...

> ===>  Patching for plan9port-20180117
> Segmentation fault (core dumped)
> *** Warning in /usr/ports/plan9/plan9port: "uname -m" returned non-zero
>

dmesg from this box, please.


Philip Guenther

Compilations errors with plan9port on 2018/04/05 snapshot

[Patrick Marchand]

Output of compiling plan9port on amd64 with the april 5 snaphot

===> plan9port-20180117 depends on: bzip2-* -> bzip2-1.0.6p8
===>  Verifying specs:  X11 Xext c m pthread util fontconfig freetype z
===>  found X11.16.1 Xext.13.0 c.92.3 m.10.1 pthread.25.1 util.13.0
fontconfig.11.0 freetype.28.2 z.5.0
===>  Checking files for plan9port-20180117
>> Fetch
>> https://github.com/9fans/plan9port/archive/019be4481fee53a999ccb73c78e40df5f408b24e.tar.gz
>> Fetch http://pdos.lcs.mit.edu/~rsc/pgw.tar.bz2
ftp: SSL write error: name `pdos.lcs.mit.edu' not present in server
certificate
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/plan9port/pgw.tar.bz2
pgw.tar.bz2  100%
|***|
9184 KB00:11
>> Fetch http://pdos.lcs.mit.edu/~rsc/software/plan9/roget.tar.bz2
ftp: SSL write error: name `pdos.lcs.mit.edu' not present in server
certificate
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/plan9port/roget.tar.bz2
roget.tar.bz2 100%
|**|
471 KB00:01
>> Fetch http://pdos.lcs.mit.edu/~rsc/scat.tgz
ftp: SSL write error: name `pdos.lcs.mit.edu' not present in server
certificate
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/plan9port/scat.tgz
scat.tgz 100%
|***|
5024 KB00:09
>> (SHA256) plan9port/019be4481fee53a999ccb73c78e40df5f408b24e.tar.gz:
>> OK
>> (SHA256) plan9port/pgw.tar.bz2: OK
>> (SHA256) plan9port/roget.tar.bz2: OK
>> (SHA256) plan9port/scat.tgz: OK
===>  Extracting for plan9port-20180117
cd
/usr/obj/ports/plan9port-20180117/plan9port-019be4481fee53a999ccb73c78e40df5f408b24e/dict
&& tar xjf /usr/ports/distfiles/plan9port/pgw.tar.bz2
cd
/usr/obj/ports/plan9port-20180117/plan9port-019be4481fee53a999ccb73c78e40df5f408b24e/dict
&& tar xjf /usr/ports/distfiles/plan9port/roget.tar.bz2
cd
/usr/obj/ports/plan9port-20180117/plan9port-019be4481fee53a999ccb73c78e40df5f408b24e/sky
&& tar xzf /usr/ports/distfiles/plan9port/scat.tgz
===>  Patching for plan9port-20180117
Segmentation fault (core dumped)
*** Warning in /usr/ports/plan9/plan9port: "uname -m" returned non-zero
status (/usr/ports/infrastructure/mk/arch-defines.mk:12)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: 

Re: bsd.rd source

[Mike Burns]

On 2018-04-05 15.29.22 -0600, ch...@ccmach14.org wrote:
> Hello - will someone please tell me where I can find the source for
> bsd.rd?

That's the kernel. Two ways to start reading:

/usr/src/distrib - this is how bsd.rd itself is built.
/usr/src/sys/kern/init_main.c - this is the main function for the kernel.

Re: bsd.rd source

[Aaron Mason]

Same place as the bsd kernel itself - they're both built from the same source.

On Fri, Apr 6, 2018 at 7:29 AM,   wrote:
> Hello - will someone please tell me where I can find the source for bsd.rd?
> Thanks
>



-- 
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse

Re: X: WaitForSomething(): poll: Invalid argument

[Stephane HUC "CIOTBSD"]

Oh, i found my problem. I configured options wsconcfg with wsconsctl.

When i modify, either 'display.vblank=on', or 'mouse.tp.tapping=1', X
not recognize those values, and the daemon fill logs! :(

Maybe I'm doing this wrong!?



And sorry, for the several posting. Few bad problems in same time. My
apologize.


Le 04/05/18 à 10:41, Martin Pieuchot a écrit :
> On 04/04/18(Wed) 12:02, Stephane HUC "PengouinBSD" wrote:
>> Hi all.
>>
>> How can identify what trouble X?
>> I run OpenBSD 6.3 - amd64 on my laptop Dell Alienware 13.
>>
>> Something fill both logs:
>> - /var/log/Xorg.0.log
>> - /var/log/xenodm.log
>>
>> with this repeated message : "WaitForSomething(): poll: Invalid argument"
>>
>> I use a custom xorg.conf, as:
> Can you see the problem if you remove your custom xorg.conf?

-- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<

Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net

Re: OpenSSH 7.7 default ciphers

[Damien Miller]

Thanks - I just committed a fix (having missed that Otto already
included a patch beyond the bottom of my xterm -- sorry)

On Thu, 5 Apr 2018, Otto Moerbeek wrote:

> On Thu, Apr 05, 2018 at 01:51:51PM +0200, Renaud Allard wrote:
> 
> > Hello,
> > 
> > The man page for openssh 7.7 for Ciphers specifications mentions:
> > 
> > The default is:
> > chacha20-poly1...@openssh.com,
> > aes128-ctr,aes192-ctr,aes256-ctr,
> > aes128-...@openssh.com,aes256-...@openssh.com,
> > aes128-cbc,aes192-cbc,aes256-cbc
> > 
> > 
> > However, ssh doesn't use the last line in that list:
> > $ ssh -G 127.0.0.1 |grep ciphers
> > ciphers 
> > chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
> > 
> > The changelog doesn't mention any change in the ciphers either.
> > 
> > 
> > 
> > Regards
> > 
> 
> The man ssh_config page is wrong (sshd_config is right).
> 
>   -Otto
> 
> Index: ssh_config.5
> ===
> RCS file: /cvs/src/usr.bin/ssh/ssh_config.5,v
> retrieving revision 1.268
> diff -u -p -r1.268 ssh_config.5
> --- ssh_config.5  23 Feb 2018 07:38:09 -  1.268
> +++ ssh_config.5  5 Apr 2018 12:08:36 -
> @@ -425,8 +425,7 @@ The default is:
>  .Bd -literal -offset indent
>  chacha20-poly1...@openssh.com,
>  aes128-ctr,aes192-ctr,aes256-ctr,
> -aes128-...@openssh.com,aes256-...@openssh.com,
> -aes128-cbc,aes192-cbc,aes256-cbc
> +aes128-...@openssh.com,aes256-...@openssh.com
>  .Ed
>  .Pp
>  The list of available ciphers may also be obtained using
> 

bsd.rd source

[chuck]

Hello - will someone please tell me where I can find the source for 
bsd.rd? Thanks

Re: X: WaitForSomething(): poll: Invalid argument

[Martin Pieuchot]

On 04/04/18(Wed) 12:02, Stephane HUC "PengouinBSD" wrote:
> Hi all.
> 
> How can identify what trouble X?
> I run OpenBSD 6.3 - amd64 on my laptop Dell Alienware 13.
> 
> Something fill both logs:
> - /var/log/Xorg.0.log
> - /var/log/xenodm.log
> 
> with this repeated message : "WaitForSomething(): poll: Invalid argument"
> 
> I use a custom xorg.conf, as:

Can you see the problem if you remove your custom xorg.conf?

Re: Netgear AC6100 Wireless adapter support

[Manuel Solis]

Ok, no problem,

Please, continue saving the world one project at the time!

Thank you for answer :)

El jue., 5 de abr. de 2018 16:07, Stefan Sperling  escribió:

> On Thu, Apr 05, 2018 at 08:59:31PM +, Manuel Solis wrote:
> > Since i am not a dev nor i know how to program, Mr Stefan, would you help
> > me with that?
>
> No. I am already juggling enough projects at the moment. Sorry.
>

Re: Netgear AC6100 Wireless adapter support

[Stefan Sperling]

On Thu, Apr 05, 2018 at 08:59:31PM +, Manuel Solis wrote:
> Since i am not a dev nor i know how to program, Mr Stefan, would you help
> me with that?

No. I am already juggling enough projects at the moment. Sorry.

Re: Netgear AC6100 Wireless adapter support

[Manuel Solis]

Thank you for your answer, i will save that bucks.

Instead i would like to contribute to port it,

Since i am not a dev nor i know how to program, Mr Stefan, would you help
me with that?


El jue., 5 de abr. de 2018 15:48, Stefan Sperling  escribió:

> On Thu, Apr 05, 2018 at 07:44:42PM +, Manuel Solis wrote:
> > First of all: contratulations for 6.3 and happy upgrades!
> >
> > Dear Misc guys,
> >
> > Do you happend to know if the NETGEAR AC6100 WIRELESS USB adapter is
> > supported by OpenBSD?
>
> Not at present.
>
> It looks like FreeBSD has code for this device in sys/dev/rtwn/rtl8812a/
> which could be ported, though.
>
> FreeBSD's rtwn driver was derived from ours and then extended with a lot
> of changes that weren't ported back to OpenBSD due to lack of developer
> time.

Re: Netgear AC6100 Wireless adapter support

[Stefan Sperling]

On Thu, Apr 05, 2018 at 07:44:42PM +, Manuel Solis wrote:
> First of all: contratulations for 6.3 and happy upgrades!
> 
> Dear Misc guys,
> 
> Do you happend to know if the NETGEAR AC6100 WIRELESS USB adapter is
> supported by OpenBSD?

Not at present.

It looks like FreeBSD has code for this device in sys/dev/rtwn/rtl8812a/
which could be ported, though.

FreeBSD's rtwn driver was derived from ours and then extended with a lot
of changes that weren't ported back to OpenBSD due to lack of developer
time.

Re: Confusing with 'perl /usr/ports/infrastructure/bin/clean-old-distfiles' script

[Marc Espie]

On Thu, Apr 05, 2018 at 07:42:31PM +0100, Nigel Taylor wrote:
> On 04/05/18 17:52, Denis wrote:
> > I try to clean 'old' distfiles by a command 'perl
> > /usr/ports/infrastructure/bin/clean-old-distfiles' without success.
> > 
> > Getting this:
> > 'No history to prune at
> > /usr/ports/infrastructure/bin/clean-old-distfiles line 104'
> > 
> > What ports manipulations I have done before run 'clean-old-distfiles'
> > perl script?
> > 
> > Denis
> > 
> > 
> > 
> history file is created by dpb see man dpb
> look at dpb option -D HISTORY_ONLY

Also, see clean-old-distfiles(1) which is 100% clear that it is directly
linked to dpb...

Netgear AC6100 Wireless adapter support

[Manuel Solis]

First of all: contratulations for 6.3 and happy upgrades!

Dear Misc guys,

Do you happend to know if the NETGEAR AC6100 WIRELESS USB adapter is
supported by OpenBSD?

Sorry for asking but i have bought 3 usb wifis adapter and 2 internal wifi
card for my lenovo g40 and none have worked. I understand the blob and
closed licenses thing, but it would be great if anyone could share your
experience with it before buying it :)

I have a panasonic cf30 and a samsung laptop working just fine, so i
suppouse with certain confidence that it is not a config issue but hw
support.

Thank you all,

Manuel

Re: Confusing with 'perl /usr/ports/infrastructure/bin/clean-old-distfiles' script

[Nigel Taylor]

On 04/05/18 17:52, Denis wrote:
> I try to clean 'old' distfiles by a command 'perl
> /usr/ports/infrastructure/bin/clean-old-distfiles' without success.
> 
> Getting this:
> 'No history to prune at
> /usr/ports/infrastructure/bin/clean-old-distfiles line 104'
> 
> What ports manipulations I have done before run 'clean-old-distfiles'
> perl script?
> 
> Denis
> 
> 
> 
history file is created by dpb see man dpb
look at dpb option -D HISTORY_ONLY

Re: Status of X i386 openbsd 6.2 on x200

[flipchan]

It works when installing but it wont boot 



On their website it says: "
Installing OpenBSD with full disk encryption

Not working. You can modify the above procedure (installation w/o encryption) 
to install OpenBSD using full disk encryption, and it appears to work, except 
that it’s not yet clear how to actually boot an OpenBSD+FDE installation using 
libreboot+Grub2. If you get it working, please let us know."

Site: https://libreboot.org/docs/bsd/openbsd.html

On April 5, 2018 4:39:56 PM UTC, Jordan Geoghegan  
wrote:
>What is it that prevents full disk encryption? I have been wanting a 
>libreboot machine for travel, but Full disk encryption is more
>important 
>that a clean bios when travelling.
>
>Thanks for your time,
>
>Jordan
>
>
>On 04/04/18 15:23, flipchan wrote:
>> The amd64 fs file for 6.2 is working good i know got it running with
>libreboot which is cool, libreboot doesnt support full disk encryption 
>which sucks but i am glad that it works .
>>
>> On April 2, 2018 7:26:58 PM UTC, Markus Lude 
>wrote:
>>> On Sun, Apr 01, 2018 at 09:41:07PM +, flipchan wrote:
 Hello all,

 I have tried to installed 6.1 and 6.2 on a thinkpad x200 it works
>but
>>> X does work ...
 Its works great with 6.0 but then i dont get the good 6.2 packages
>>> and features such as syspatch.

 It seems lika well known problem:
 https://marc.info/?l=openbsd-bugs=150506076421862=2


 Does anyone know the status of this/ if anyone is working on this ?
>>> The problem still exists. The drm diff back then was quite huge and
>I
>>> am
>>> unable to break it down in smaller chunks to see where the cause
>>> therein
>>> is.
>>> The T61 is quite old and still runs with 6.1.
>>> It is new for me that newer Thinkpads do have the same problem.
>Could
>>> you please post a trace of your crash?
>>>
>>> Regards,
>>> Markus

-- 
Take Care Sincerely flipchan layerprox dev

Confusing with 'perl /usr/ports/infrastructure/bin/clean-old-distfiles' script

[Denis]

I try to clean 'old' distfiles by a command 'perl
/usr/ports/infrastructure/bin/clean-old-distfiles' without success.

Getting this:
'No history to prune at
/usr/ports/infrastructure/bin/clean-old-distfiles line 104'

What ports manipulations I have done before run 'clean-old-distfiles'
perl script?

Denis

Re: Status of X i386 openbsd 6.2 on x200

[Jordan Geoghegan]

What is it that prevents full disk encryption? I have been wanting a 
libreboot machine for travel, but Full disk encryption is more important 
that a clean bios when travelling.


Thanks for your time,

Jordan


On 04/04/18 15:23, flipchan wrote:

The amd64 fs file for 6.2 is working good i know got it running with libreboot 
which is cool, libreboot doesnt support full disk encryption  which sucks but i 
am glad that it works .

On April 2, 2018 7:26:58 PM UTC, Markus Lude  wrote:

On Sun, Apr 01, 2018 at 09:41:07PM +, flipchan wrote:

Hello all,

I have tried to installed 6.1 and 6.2 on a thinkpad x200 it works but

X does work ...

Its works great with 6.0 but then i dont get the good 6.2 packages

and features such as syspatch.


It seems lika well known problem:
https://marc.info/?l=openbsd-bugs=150506076421862=2


Does anyone know the status of this/ if anyone is working on this ?

The problem still exists. The drm diff back then was quite huge and I
am
unable to break it down in smaller chunks to see where the cause
therein
is.
The T61 is quite old and still runs with 6.1.
It is new for me that newer Thinkpads do have the same problem. Could
you please post a trace of your crash?

Regards,
Markus

Re: Intel Microcode Guidance: Abandoned Processor Families and Spectre

[Netelysis Sisyleten]

On Thu, Apr 5, 2018 at 9:19 AM, Aham Brahmasmi 
wrote:

> Hello Misc,
>
> Will OpenBSD's patches for Spectre help mitigate the risk for the
> processor families which are not receiving Intel's mitigation microcode
> for Spectre/Spectre variant 2?
>
> Backdrop
> Intel has issued a Microcode Revision Guidance on April 3, 2018 [1].
> As per this guidance, some processor families will not be receiving
> the Spectre/Spectre variant 2 mitigation microcode updates from Intel.
> The reasons for this kind act of benevolence are best known to Intel.
>
> The above is my understanding based on TheRegister's article[2]. As a
> layman who understands little to nothing about Spectre or Meltdown, I
> am wondering whether OpenBSD's mitigations would be sufficient.
>
> On a side note, older IBM-era ThinkPads seem to be left out by Intel.
> ThinkPad Classic is/was for volks with lot of money. Lenovo wants to be
> Apple. I do not have words to express myself.
>
> Regards,
> ab
> [1] - https://newsroom.intel.com/wp-content/uploads/sites/11/2018/
> 04/microcode-update-guidance.pdf
> [2] - http://www.theregister.co.uk/2018/04/04/intel_spectre_
> microcode_updates/
> -|-|-|-|-|-|-|--
>
>
Sir Brahmasmi:

>From http://www.openbsd.org/63.html
- What's New
-- section - Security improvements:

OpenBSD/arm64 now uses kernel page table isolation to mitigate Spectre
variant 3 (Meltdown) attacks.

OpenBSD/armv7 and OpenBSD/arm64 now flush the Branch Target Buffer (BTB) on
processors that do speculative execution to mitigate Spectre variant 2
attacks.

-- 
Boyd Stephens

Re: Intel Microcode Guidance: Abandoned Processor Families and Spectre

[Mathieu Simon (Lists)]

Hi

Am 05.04.2018 um 16:19 schrieb Aham Brahmasmi:
> Hello Misc,
> 
> Will OpenBSD's patches for Spectre help mitigate the risk for the
> processor families which are not receiving Intel's mitigation microcode
> for Spectre/Spectre variant 2?
Someone deeper into OpenBSD can give reliable information on this topic,
I'll focus on the Notebook processors.

> Backdrop
> Intel has issued a Microcode Revision Guidance on April 3, 2018 [1].
> As per this guidance, some processor families will not be receiving
> the Spectre/Spectre variant 2 mitigation microcode updates from Intel.
> The reasons for this kind act of benevolence are best known to Intel.
> 
> The above is my understanding based on TheRegister's article[2]. As a
> layman who understands little to nothing about Spectre or Meltdown, I
> am wondering whether OpenBSD's mitigations would be sufficient.
> 
> On a side note, older IBM-era ThinkPads seem to be left out by Intel.
> ThinkPad Classic is/was for volks with lot of money. Lenovo wants to be
> Apple. I do not have words to express myself.
The last Thinkpads bearing an IBM logo were the T61's (Core 2) and a
quick search indicates already T60's (Core) had been built under Lenovo
and not anymore IBM, yet keeping the IBM logo in it for some extra time.

Also the all T400 series (Core 2 as well) which didn't bear any IBM
branding won't be receiving updated microcode and thus Lenovo is very
unlikely to release BIOS updates. It's not a move against IBM-branded
old Thinkpad models. The same applies for any other vendor unless Intel
reconsiders their decision.

For systems like the T410 (Core i gen 1, Arrandale) who haven't received
any BIOS updates yet but Intel lists as CPus who should get updated
microcode, on OpenBSD we can then load updated microcode once it is
available. Thus we are not depdendent on system and board manufacturers
to provide updated BIOS version.

A lot of machines still plenty powerful enough for casual use will be
left out by Intel in terms of microcode fixes. I'm actually interested
on how OpenBSD developers plan and eventually decide on a generic
implementation, independent of microcode updates like Linux did with
retpoline.

Anyway, thank you to those OpenBSD developers who have invested many
hours and sleepless nights in order to implement mitigations for Spectre
and Meltdown on OpenBSD no with extra time before the embargo was lifted.

-- Mathieu

Intel Microcode Guidance: Abandoned Processor Families and Spectre

[Aham Brahmasmi]

Hello Misc,

Will OpenBSD's patches for Spectre help mitigate the risk for the
processor families which are not receiving Intel's mitigation microcode
for Spectre/Spectre variant 2?

Backdrop
Intel has issued a Microcode Revision Guidance on April 3, 2018 [1].
As per this guidance, some processor families will not be receiving
the Spectre/Spectre variant 2 mitigation microcode updates from Intel.
The reasons for this kind act of benevolence are best known to Intel.

The above is my understanding based on TheRegister's article[2]. As a
layman who understands little to nothing about Spectre or Meltdown, I
am wondering whether OpenBSD's mitigations would be sufficient.

On a side note, older IBM-era ThinkPads seem to be left out by Intel.
ThinkPad Classic is/was for volks with lot of money. Lenovo wants to be
Apple. I do not have words to express myself.

Regards,
ab
[1] - 
https://newsroom.intel.com/wp-content/uploads/sites/11/2018/04/microcode-update-guidance.pdf
[2] - http://www.theregister.co.uk/2018/04/04/intel_spectre_microcode_updates/
-|-|-|-|-|-|-|--

Re: texmacs on 6.2

[Rudolf Sykora]

>> Try to fix TeXmacs so that it builds with clang; note that there are new
>> releases upstream.

According to TeXmacs developers:

"The default compiler for TeXmacs in linux became clang a few months ago. So I
guess it is just a matter of fixing building issues in OpenBSD..."

Ruda

Re: OpenSSH 7.7 default ciphers

[Otto Moerbeek]

On Thu, Apr 05, 2018 at 01:51:51PM +0200, Renaud Allard wrote:

> Hello,
> 
> The man page for openssh 7.7 for Ciphers specifications mentions:
> 
> The default is:
> chacha20-poly1...@openssh.com,
> aes128-ctr,aes192-ctr,aes256-ctr,
> aes128-...@openssh.com,aes256-...@openssh.com,
> aes128-cbc,aes192-cbc,aes256-cbc
> 
> 
> However, ssh doesn't use the last line in that list:
> $ ssh -G 127.0.0.1 |grep ciphers
> ciphers 
> chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
> 
> The changelog doesn't mention any change in the ciphers either.
> 
> 
> 
> Regards
> 

The man ssh_config page is wrong (sshd_config is right).

-Otto

Index: ssh_config.5
===
RCS file: /cvs/src/usr.bin/ssh/ssh_config.5,v
retrieving revision 1.268
diff -u -p -r1.268 ssh_config.5
--- ssh_config.523 Feb 2018 07:38:09 -  1.268
+++ ssh_config.55 Apr 2018 12:08:36 -
@@ -425,8 +425,7 @@ The default is:
 .Bd -literal -offset indent
 chacha20-poly1...@openssh.com,
 aes128-ctr,aes192-ctr,aes256-ctr,
-aes128-...@openssh.com,aes256-...@openssh.com,
-aes128-cbc,aes192-cbc,aes256-cbc
+aes128-...@openssh.com,aes256-...@openssh.com
 .Ed
 .Pp
 The list of available ciphers may also be obtained using

OpenSSH 7.7 default ciphers

[Renaud Allard]

Hello,

The man page for openssh 7.7 for Ciphers specifications mentions:

The default is:
chacha20-poly1...@openssh.com,
aes128-ctr,aes192-ctr,aes256-ctr,
aes128-...@openssh.com,aes256-...@openssh.com,
aes128-cbc,aes192-cbc,aes256-cbc


However, ssh doesn't use the last line in that list:
$ ssh -G 127.0.0.1 |grep ciphers
ciphers 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com


The changelog doesn't mention any change in the ciphers either.



Regards



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Did OpenBSD just go green?

[Mihai Popescu]

> ... did OpenBSD go green with 6.3 ...

You know, OpenBSD is not working so go on your smart tv or microwave
owen for the moment.
They struggle to meet the Green standard on house appliances these days.

Re: iwi(4) fatal firmware error

[Stefan Sperling]

On Wed, Apr 04, 2018 at 12:20:03PM -0500, Ax0n wrote:
> I have a Motorola ML900 which seems to be running OpenBSD with X and
> WindowMaker just fine. Every few hours it gets a group of errors within the
> span of a few seconds (about 1 second between them in /var/log/messages)
> 
> Apr  4 04:30:01 luggy /bsd: iwi0: fatal firmware error
> Apr  4 05:17:37 luggy /bsd: iwi0: fatal firmware error
> Apr  4 05:17:39 luggy /bsd: iwi0: unknown authentication state 1
> Apr  4 05:17:40 luggy /bsd: iwi0: reused group key update received from
> 60:38:e0:89:9b:dc
> Apr  4 06:51:05 luggy /bsd: iwi0: fatal firmware error
> Apr  4 06:51:06 luggy /bsd: iwi0: unknown authentication state 1
> Apr  4 06:51:07 luggy /bsd: iwi0: reused group key update received from
> 60:38:e0:89:9b:dc
> Apr  4 10:11:48 luggy /bsd: iwi0: fatal firmware error
> Apr  4 10:11:51 luggy /bsd: iwi0: unknown authentication state 1
> Apr  4 10:11:52 luggy /bsd: iwi0: reused group key update received from
> 60:38:e0:89:9b:dc
> 
> I was seeing this same behavior with 6.2-STABLE, which I just installed a
> few weeks ago.
> 
> Full dmesg (before any of the above errors) is below.

Is this a purely cosmetic issue or does it actually prevent your
wifi connection from working?

These looks like potentially harmless errors which happen during association.
Does the driver recover from these errors automatically? It should be able to.

As to why the firmware reports such errors: We have no idea. It's a black box.

Re: 6.3 amd64 in VirtualBox - keyboard

[kasak]

05.04.2018 01:55, Will Backman пишет:
Anyone else seeing an unresponsive keyboard with 6.3 release amd64 
when running in VirtualBox?
bsd.rd installer works. After install, cannot log in because keyboard 
won't accept input.

6.2 works fine.
Installed current (as of 4/4) and keyboard works.

I had unresponsive keyboard in bsd.rd, when i was updating to 6.3 with 
asus ikvm. Luckily, the soft keyboard worked.