Re: update to RC4 from RC3 shutdown regression

[Andrey Fesenko]

On Wed, Mar 31, 2021 at 7:37 PM Glen Barber  wrote:
>
> On Wed, Mar 31, 2021 at 11:22:58AM -0500, Antonio Olivares wrote:
> > On Wed, Mar 31, 2021 at 11:03 AM Glen Barber  wrote:
> > >
> > > On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
> > > > Dear all,
> > > >
> > > > after updating to RC4 with
> > > > # freebsd-update -r upgrade 13.0RC4
> > > > When I shutdown, I get error messages AE_??? PCI
> > > >
> > > >
> > > > Press any key to reboot
> > > >
> > > > It shutdown before from 13.0-BETA4 updated all the way to RC3. I can 
> > > > save a
> > > > screenshot if needed.  Thanks.
> > >
> > > Please do.
> > >
> >
> > Dear Sir,
> >
> > I shutdown today to see if I got the same message, but I did not.  If
> > I do encounter this again, I will do my best to save a screenshot and
> > post it.
> >
>
> Okay, thank you.
>

Hello
my build box kvm-efi (centos edk2.git-ovmf-x64
0-20201222.1581.g98ff7e3c63) buider start  endless freeze reboot and
shutdown -p now (set hw.efi.poweroff=0 not fix)
virtualbox windows host, reboot work fine shutdown -p require set
hw.efi.poweroff=0
FreeBSD new uefi-edk2-bhyve g20210214,2 work fine,
uefi-edk2-bhyve-0.2_1,1 shutdown -p require set hw.efi.poweroff=0 (not
regression RC3)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 13.0-RC3 bison causes tputs SIGSEGV

[Thomas Dickey]

On Wed, Mar 31, 2021 at 06:49:55PM -0400, Thomas Dickey wrote:
> On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote:
> > 
> > > On 31 Mar 2021, at 15:53, Henric Jungheim  wrote:
> > > 
> > >> 
> > >> Knowing that would help me see whether the problem is faulty 
> > >> initialization
> > >> from libtextstyle (i.e., the SCREEN pointer is null, making the path via
> > >> the static structure), or some ifdef-combination in ncurses that I've
> > >> neglected (i.e., a flaw in the pointer juggling).
> > 
> > I’ve observed that the application in question calls:
> > 
> >   /* Create the output styled stream.  */
> >   pk_ostream =
> > (color_mode == color_html
> >  ? html_styled_ostream_create (file_ostream_create (stdout),
> >style_file_name)
> >  : styled_ostream_create (STDOUT_FILENO, "(stdout)",
> >   TTYCTL_AUTO, style_file_name));
> > 
> > Does it make any difference?
> 
> I don't know yet.  I've been setting up a build for bison+libtextstyle
> so that I can study it firsthand (and use valgrind, etc., to look for
> problems).

...valgrind on Debian/testing (iirc, valgrind doesn't work with BSDs).

However, aside from the cgetent stuff, the terminfo part of my test-setup
matches what's in FreeBSD's build for ncurses.  valgrind finds nothing
amiss with the tests that I've done to exercise the libtextstyle code.
(address-sanitizer may).

By the way, ktruss could show what files are opened in your configuration,
and a log from that would tell me if it's reading via the termcap interface.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Re: 13.0-RC3 bison causes tputs SIGSEGV

[Thomas Dickey]

On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote:
> 
> > On 31 Mar 2021, at 15:53, Henric Jungheim  wrote:
> > 
> >> 
> >> Knowing that would help me see whether the problem is faulty initialization
> >> from libtextstyle (i.e., the SCREEN pointer is null, making the path via
> >> the static structure), or some ifdef-combination in ncurses that I've
> >> neglected (i.e., a flaw in the pointer juggling).
> 
> I’ve observed that the application in question calls:
> 
>   /* Create the output styled stream.  */
>   pk_ostream =
> (color_mode == color_html
>  ? html_styled_ostream_create (file_ostream_create (stdout),
>style_file_name)
>  : styled_ostream_create (STDOUT_FILENO, "(stdout)",
>   TTYCTL_AUTO, style_file_name));
> 
> Does it make any difference?

I don't know yet.  I've been setting up a build for bison+libtextstyle
so that I can study it firsthand (and use valgrind, etc., to look for
problems).

That chunk is just the initialization, while the problem appears later.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Re: freebsd 13 ryzen micro stutter

[sm]

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 13.0-RC3 bison causes tputs SIGSEGV

[Juraj Lutter]

> On 31 Mar 2021, at 15:53, Henric Jungheim  wrote:
> 
>> 
>> Knowing that would help me see whether the problem is faulty initialization
>> from libtextstyle (i.e., the SCREEN pointer is null, making the path via
>> the static structure), or some ifdef-combination in ncurses that I've
>> neglected (i.e., a flaw in the pointer juggling).

I’ve observed that the application in question calls:

  /* Create the output styled stream.  */
  pk_ostream =
(color_mode == color_html
 ? html_styled_ostream_create (file_ostream_create (stdout),
   style_file_name)
 : styled_ostream_create (STDOUT_FILENO, "(stdout)",
  TTYCTL_AUTO, style_file_name));

Does it make any difference?

thanks
otis
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Update to the 13.0-RELEASE schedule

[Daniel Morante via freebsd-current]

Also, this release seems to have gotten a lot more attention than 
usual.  So probably more people are testing.


On 3/31/21 1:24 PM, Rainer Duffner wrote:



Am 31.03.2021 um 17:58 schrieb Glen Barber :

A small set of updates that we consider blocking the 13.0 release have
been brought to our attention.  As such, the 13.0-RELEASE schedule has
been updated to include a fifth release candidate (RC5).

The updated schedule is available on the FreeBSD Project website:

https://www.freebsd.org/releases/13.0R/schedule/

As usual, we will continue to consider critical bug fixes only for the
duration of this release cycle.

Thank you for your cooperation, and for your patience.

Glen
On behalf of:   re@




The truth is that a lot people don’t really start testing until the later 
release candidates.

So, having more of these release candidates with just refinements is a good 
thing, IMHO.



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Update to the 13.0-RELEASE schedule

[Rainer Duffner]

> Am 31.03.2021 um 17:58 schrieb Glen Barber :
> 
> A small set of updates that we consider blocking the 13.0 release have
> been brought to our attention.  As such, the 13.0-RELEASE schedule has
> been updated to include a fifth release candidate (RC5).
> 
> The updated schedule is available on the FreeBSD Project website:
> 
> https://www.freebsd.org/releases/13.0R/schedule/
> 
> As usual, we will continue to consider critical bug fixes only for the
> duration of this release cycle.
> 
> Thank you for your cooperation, and for your patience.
> 
> Glen
> On behalf of: re@
> 



The truth is that a lot people don’t really start testing until the later 
release candidates.

So, having more of these release candidates with just refinements is a good 
thing, IMHO.



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 13.0-RC3 bison causes tputs SIGSEGV

[Henric Jungheim]

On Tue, Mar 30, 2021 at 08:48:03PM -0400, Thomas Dickey wrote:
> On Tue, Mar 30, 2021 at 08:37:22AM +0200, Juraj Lutter wrote:
> > Hi,
> > 
> > very similar behavior is observed in editors/poke, on recent 13.0-STABLE 
> > (stable/13-85ad493677a2):
> > 
> > (lldb) bt
> > * thread #1, name = 'poke', stop reason = signal SIGSEGV: invalid address 
> > (fault address: 0x0)
> >   * frame #0: 0x
> > frame #1: 0x0008009ed30a 
> > libncursesw.so.9`delay_output_sp(sp=0x, ms=) 
> > at lib_tputs.c:104:6
> 
> The SCREEN pointer sp is null here: which could occur if there was
> no matching terminal description.  I noticed that libtextstyle doesn't
> give up on that error, but just proceeds along as though other functions
> which would return the terminal capabilities will somehow return valid
> data when the terminal database isn't initialized.
> 
> > frame #2: 0x0008009edb81 libncursesw.so.9`tputs_sp [inlined] 
> > delay_output(ms=) at lib_tputs.c:116:12
> > frame #3: 0x0008009edb72 
> > libncursesw.so.9`tputs_sp(sp=, string="", affcnt=1, 
> > outc=) at lib_tputs.c:422
> > frame #4: 0x0008009edcfb 
> > libncursesw.so.9`tputs(string="4f0fdc740005bebaf92e5a2e", affcnt=1, 
> > outc=(libtextstyle.so.0`out_char at term-ostream.oo.c:1198)) at 
> > lib_tputs.c:444:12
> 
> well yes...  The caller is supposed to provide outch via tputs, 
> which isn't a parameter of delay_output (but delay_output needs it).
> ncurses saves/restores that pointer in the SCREEN structure --
> if it's initialized -- otherwise in a static structure.  It's made
> a little more complicated since some paths use stdout and others
> use ncurses' buffering via outch (which may be unrelated to stdout).
> 
> That pointer-juggling dates back to late 2009 -- but of course other
> changes have occurred since then.
> 
> So... the question I have is what is $TERM in this case,
> and where is the related terminal description (in terminfo or termcap).

In the example in my original email, $TERM was "xterm-256color"
(connected through "Windows Terminal" running MS' ssh on Win10).

> 
> Knowing that would help me see whether the problem is faulty initialization
> from libtextstyle (i.e., the SCREEN pointer is null, making the path via
> the static structure), or some ifdef-combination in ncurses that I've
> neglected (i.e., a flaw in the pointer juggling).
> 
> > frame #5: 0x000800424bb0 
> > libtextstyle.so.0`out_hyperlink_change(stream=0x000800e3d000, 
> > new_hyperlink=0x0008018bd600, async_safe=false) at 
> > term-ostream.oo.c:1586:7
> > frame #6: 0x00080042579c 
> > libtextstyle.so.0`out_attr_change(stream=0x000800e3d000, 
> > new_attr=attributes_t @ 0x7fffe608) at term-ostream.oo.c:1737:11
> > frame #7: 0x000800424f3b 
> > libtextstyle.so.0`output_buffer(stream=0x000800e3d000, 
> > goal_attr=attributes_t @ 0x7fffe690) at term-ostream.oo.c:1906:11
> > frame #8: 0x0008004223b2 
> > libtextstyle.so.0`term_ostream__write_mem(stream=0x000800e3d000, 
> > data=0x00207a94, len=123) at term-ostream.oo.c:2037:11
> > frame #9: 0x000800422ed5 
> > libtextstyle.so.0`term_ostream_write_mem(first_arg=0x000800e3d000, 
> > data=0x00207a94, len=123) at term-ostream.c:2721:3
> > frame #10: 0x000800427e3f 
> > libtextstyle.so.0`term_styled_ostream__write_mem(stream=0x000800e3a000, 
> > data=0x00207a94, len=123) at term-styled-ostream.oo.c:95:3
> > frame #11: 0x000800420535 
> > libtextstyle.so.0`ostream_write_mem(first_arg=0x000800e3a000, 
> > data=0x00207a94, len=123) at ostream.c:138:3
> > frame #12: 0x0008004204ec 
> > libtextstyle.so.0`ostream_write_str(stream=0x000800e3a000, 
> > string=".\nThis is free software: you are free to change and redistribute 
> > it.\nThere is NO WARRANTY, to the extent permitted by law.\n") at 
> > ostream.oo.c:35:3
> > frame #13: 0x00210add poke`pk_puts(str=".\nThis is free 
> > software: you are free to change and redistribute it.\nThere is NO 
> > WARRANTY, to the extent permitted by law.\n") at pk-term.c:257:3
> > 
> > 
> > Iny my case, there is a NULL pointer dereference in delay_output_ch(), 
> > where my_outch is NULL:
> > 
> > frame #0: 0x0008009ed2da 
> > libncursesw.so.9`delay_output_sp(sp=0x, ms=4) at 
> > lib_tputs.c:103:22
> >100  register int nullcount;
> >101
> >102  nullcount = (ms * _nc_baudrate(ospeed)) / (BAUDBYTE * 1000);
> > -> 103  for (_nc_nulls_sent += nullcount; nullcount > 0; 
> > nullcount--)
> >104  my_outch(NCURSES_SP_ARGx PC);
> >105  if (my_outch == NCURSES_SP_NAME(_nc_outch))
> >106  NCURSES_SP_NAME(_nc_flush) (NCURSES_SP_ARG);
> > 
> > Application is using term_styled_ostream_create() that does not initialize 
> > default_attr.
> > 
> > > On 30 Mar 2021, at 01:31, Thomas Dickey  

Re: Update to the 13.0-RELEASE schedule

[The Doctor via freebsd-current]

On Wed, Mar 31, 2021 at 03:58:51PM +, Glen Barber wrote:
> A small set of updates that we consider blocking the 13.0 release have
> been brought to our attention.  As such, the 13.0-RELEASE schedule has
> been updated to include a fifth release candidate (RC5).
> 
> The updated schedule is available on the FreeBSD Project website:
> 
> https://www.freebsd.org/releases/13.0R/schedule/
> 
> As usual, we will continue to consider critical bug fixes only for the
> duration of this release cycle.
> 
> Thank you for your cooperation, and for your patience.
> 
> Glen
> On behalf of: re@
> 

I rather that than a buggy realease.

Good show.

I will continue to test on my workstation running
a Supermicro X10sL7-f

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b  
We cannot change human failings by ridding ourselves of machines.  -unknown
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: update to RC4 from RC3 shutdown regression

[Glen Barber]

On Wed, Mar 31, 2021 at 11:22:58AM -0500, Antonio Olivares wrote:
> On Wed, Mar 31, 2021 at 11:03 AM Glen Barber  wrote:
> >
> > On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
> > > Dear all,
> > >
> > > after updating to RC4 with
> > > # freebsd-update -r upgrade 13.0RC4
> > > When I shutdown, I get error messages AE_??? PCI
> > >
> > >
> > > Press any key to reboot
> > >
> > > It shutdown before from 13.0-BETA4 updated all the way to RC3. I can save 
> > > a
> > > screenshot if needed.  Thanks.
> >
> > Please do.
> >
> 
> Dear Sir,
> 
> I shutdown today to see if I got the same message, but I did not.  If
> I do encounter this again, I will do my best to save a screenshot and
> post it.
> 

Okay, thank you.

Glen



signature.asc
Description: PGP signature

Re: update to RC4 from RC3 shutdown regression

[Antonio Olivares]

On Wed, Mar 31, 2021 at 11:03 AM Glen Barber  wrote:
>
> On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
> > Dear all,
> >
> > after updating to RC4 with
> > # freebsd-update -r upgrade 13.0RC4
> > When I shutdown, I get error messages AE_??? PCI
> >
> >
> > Press any key to reboot
> >
> > It shutdown before from 13.0-BETA4 updated all the way to RC3. I can save a
> > screenshot if needed.  Thanks.
>
> Please do.
>
> Glen
>

Dear Sir,

I shutdown today to see if I got the same message, but I did not.  If
I do encounter this again, I will do my best to save a screenshot and
post it.

Best Regards,


Antonio
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: java web start / error

[Antonio Olivares]

On Fri, Mar 5, 2021 at 11:25 AM Graham Perrin  wrote:
>
> On 05/03/2021 14:01, Antonio Olivares wrote:
> > On Thu, Mar 4, 2021 at 8:39 PM Graham Perrin  wrote:
> >> On 05/03/2021 00:53, Antonio Olivares wrote:
> >>> … It had worked before since a while.  But 2 updates ago I see this error
> >>> message on 12.2-RELEASE-amd64-p4 and it also happens on 13.0-BETA4 .  How
> >>> can I troubleshoot this?  javaws was used before, it opened up an *.jlnp
> >>> file.  Upon successfully loading an online gradebook is started.  I had
> >>> been using it successfully for several FreeBSD releases since 8.1/8.2. …
> >> With which web browsers?
> >>
> >> ___
> >> freebsd-current@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> >>
> >> worked well with firefox-esr which I use because the plugins
> >> are deprecated using the newer firefox.  Despite that it also used to
> >> work with the regular firefox.
> >>
> On rare occasions in the past, I used Opera for pages that required a
> Java plug-in.
>
> Today I find www/opera no longer working (with 14.0-CURRENT). Whilst
> non-secure  works,
>  and some other types of secure
> page no longer load. In any case,
>  it has
> been removed from ports.
>
> Maybe you can run a Java Web Start compatible browser in a jail, or
> Linuxulator?
>

I am searching for ways to troubleshoot this issue.  I prefer to try
to find a solution.
I downloaded the *.jnlp file and I have found out that javaws has been
deprecated for a long time and we run a new exectuable

olivares@deepcool:~/Downloads $ xdg-open launchGradeBook.jnlp
selected jre: /usr/local/openjdk8/jre
Warning!, Fall back in resolve_jar to hardcoded paths:
olivares@deepcool:~/Downloads $ no
Unable to use Firefox's proxy settings. Using "DIRECT" as proxy type.
selected jre: /usr/local/openjdk8/jre
Warning!, Fall back in resolve_jar to hardcoded paths:
no
Unable to use Firefox's proxy settings. Using "DIRECT" as proxy type.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-gradebook.jar
not found. Continuing.
JAR https://pschool.rgccisd.org/powerschool-gradebook/lib/commons-codec-1.9.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/commons-httpclient-3.0.1.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/commons-lang3-3.3.1.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/commons-logging-1.0.4.jar
not found. Continuing.
JAR https://pschool.rgccisd.org/powerschool-gradebook/lib/miglayout-3.6.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/org-netbeans-swing-outline.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-coteach-api.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-httpinvoke.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-i18n-sdk.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-kudomodel-sdk.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-roles-api.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-sdk-model.jar
not found. Continuing.
JAR https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-sdk.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-sdkhttpinvoke-client.jar
not found. Continuing.
JAR https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-ui.jar
not found. Continuing.
JAR https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-util.jar
not found. Continuing.
JAR https://pschool.rgccisd.org/powerschool-gradebook/lib/ssce.jar not
found. Continuing.
JAR https://pschool.rgccisd.org/powerschool-gradebook/lib/xito-dazzle-0.7.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/powerschool-gradebook.jar
not found. Continuing.
JAR https://pschool.rgccisd.org/powerschool-gradebook/lib/commons-codec-1.9.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/commons-httpclient-3.0.1.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/commons-lang3-3.3.1.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/commons-logging-1.0.4.jar
not found. Continuing.
JAR https://pschool.rgccisd.org/powerschool-gradebook/lib/miglayout-3.6.jar
not found. Continuing.
JAR 
https://pschool.rgccisd.org/powerschool-gradebook/lib/org-netbeans-swing-outline.jar
not found. Continuing.
JAR 

Re: update to RC4 from RC3 shutdown regression

[Glen Barber]

On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
> Dear all,
> 
> after updating to RC4 with
> # freebsd-update -r upgrade 13.0RC4
> When I shutdown, I get error messages AE_??? PCI
> 
> 
> Press any key to reboot
> 
> It shutdown before from 13.0-BETA4 updated all the way to RC3. I can save a
> screenshot if needed.  Thanks.

Please do.

Glen



signature.asc
Description: PGP signature

Update to the 13.0-RELEASE schedule

[Glen Barber]

A small set of updates that we consider blocking the 13.0 release have
been brought to our attention.  As such, the 13.0-RELEASE schedule has
been updated to include a fifth release candidate (RC5).

The updated schedule is available on the FreeBSD Project website:

https://www.freebsd.org/releases/13.0R/schedule/

As usual, we will continue to consider critical bug fixes only for the
duration of this release cycle.

Thank you for your cooperation, and for your patience.

Glen
On behalf of:   re@



signature.asc
Description: PGP signature

Re: Blacklisted certificates

[Jochen Neumeister]

Am 31.03.21 um 14:24 schrieb Ronald Klop:


Van: Jochen Neumeister 
Datum: woensdag, 31 maart 2021 13:26
Aan: Christoph Moench-Tegeder , 
freebsd-current@freebsd.org

Onderwerp: Re: Blacklisted certificates



Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder:
> ## Jochen Neumeister (jon...@freebsd.org):
>
>> Why are this certificates blacklisted?
> Various reasons:
> - Symantec (which owned Thawte and VeriSign back in the time) made
>    the news in a bad way:
> 
https://www.theregister.com/2017/09/12/chrome_66_to_reject_symantec_certs/

> - some certificates are simply expired
> - some certificates use SHA-1 ("sha1WithRSAEncryption") which is
>    beyond deprecated
> - and basically "whatever Mozilla did", as the certificates are
>    imported from NSS.

how can I ignore the certificates now? So now everyone has this 
problem with an update



Greetings
Jochen

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"






Hi,

This is the proper output of installworld. So you don't have to ignore 
anything anymore. It is handled by installworld.




in the next step etcupdate has another problem. I have to delete the 
blacklist certificates manually.


#cd /usr/src && etcupdate
Conflicts remain from previous update, aborting.


Greetings
Jochen


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 13.0-RC3 bison causes tputs SIGSEGV

[Juraj Lutter]

> On 31 Mar 2021, at 15:53, Henric Jungheim  wrote:
> 
>> 
>> So... the question I have is what is $TERM in this case,
>> and where is the related terminal description (in terminfo or termcap).
> 
> In the example in my original email, $TERM was "xterm-256color"
> (connected through "Windows Terminal" running MS' ssh on Win10).


In my case, also xterm-256color, connected using iTerm2 on macOS.

otis

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Blacklisted certificates

[Kyle Evans]

On Wed, Mar 31, 2021 at 7:25 AM Ronald Klop  wrote:
>
>
> Van: Jochen Neumeister 
> Datum: woensdag, 31 maart 2021 13:26
> Aan: Christoph Moench-Tegeder , 
> freebsd-current@freebsd.org
> Onderwerp: Re: Blacklisted certificates
> >
> >
> > Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder:
> > > ## Jochen Neumeister (jon...@freebsd.org):
> > >
> > >> Why are this certificates blacklisted?
> > > Various reasons:
> > > - Symantec (which owned Thawte and VeriSign back in the time) made
> > >the news in a bad way:
> > >
> > > https://www.theregister.com/2017/09/12/chrome_66_to_reject_symantec_certs/
> > > - some certificates are simply expired
> > > - some certificates use SHA-1 ("sha1WithRSAEncryption") which is
> > >beyond deprecated
> > > - and basically "whatever Mozilla did", as the certificates are
> > >imported from NSS.
> >
> > how can I ignore the certificates now? So now everyone has this problem 
> > with an update
> >
> >
> > Greetings
> > Jochen
> >
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> >
> >
> >
>
> Hi,
>
> This is the proper output of installworld. So you don't have to ignore 
> anything anymore. It is handled by installworld.
>

I might smack it with a -q hammer, since the output's likely not
relevant to most people (certainly not there).
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Blacklisted certificates

[Ronald Klop]

Van: Jochen Neumeister 
Datum: woensdag, 31 maart 2021 13:26
Aan: Christoph Moench-Tegeder , freebsd-current@freebsd.org
Onderwerp: Re: Blacklisted certificates



Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder:
> ## Jochen Neumeister (jon...@freebsd.org):
>
>> Why are this certificates blacklisted?
> Various reasons:
> - Symantec (which owned Thawte and VeriSign back in the time) made
>the news in a bad way:
>https://www.theregister.com/2017/09/12/chrome_66_to_reject_symantec_certs/
> - some certificates are simply expired
> - some certificates use SHA-1 ("sha1WithRSAEncryption") which is
>beyond deprecated
> - and basically "whatever Mozilla did", as the certificates are
>imported from NSS.

how can I ignore the certificates now? So now everyone has this problem with an 
update


Greetings
Jochen

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"





Hi,

This is the proper output of installworld. So you don't have to ignore anything 
anymore. It is handled by installworld.

Ronald.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Blacklisted certificates

[Michael Gmelin]

On Wed, 31 Mar 2021 13:02:21 +0200
Christoph Moench-Tegeder  wrote:

> ## Jochen Neumeister (jon...@freebsd.org):
> 
> > Why are this certificates blacklisted?  
> 
> Various reasons:
> - Symantec (which owned Thawte and VeriSign back in the time) made
>   the news in a bad way:
>   https://www.theregister.com/2017/09/12/chrome_66_to_reject_symantec_certs/
> - some certificates are simply expired
> - some certificates use SHA-1 ("sha1WithRSAEncryption") which is
>   beyond deprecated

The hashing algorithm (SHA-1) doesn't matter in case of trusted root
CAs though, as they're self-signed anyway - you trust the certificate
and not the signature in this case. Therefore, keeping them in for
compatibility reasons can make sense to prevent people from having to
maintain their own local trusted CA cert lists.

Probably doesn't matter so much in this specific case, but I remember
when security/ca_root_nss removed MD5 self-signed root CAs and the
world of pain I was in as a result of that decision, as legitimate
certificates that worked in all major browsers would be
suddenly considered insecure by my servers.

-m

> - and basically "whatever Mozilla did", as the certificates are
>   imported from NSS.
> 
> Regards,
> Christoph
> 



-- 
Michael Gmelin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Blacklisted certificates

[Jochen Neumeister]

Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder:

## Jochen Neumeister (jon...@freebsd.org):


Why are this certificates blacklisted?

Various reasons:
- Symantec (which owned Thawte and VeriSign back in the time) made
   the news in a bad way:
   https://www.theregister.com/2017/09/12/chrome_66_to_reject_symantec_certs/
- some certificates are simply expired
- some certificates use SHA-1 ("sha1WithRSAEncryption") which is
   beyond deprecated
- and basically "whatever Mozilla did", as the certificates are
   imported from NSS.


how can I ignore the certificates now? So now everyone has this problem 
with an update



Greetings
Jochen

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Blacklisted certificates

[Christoph Moench-Tegeder]

## Jochen Neumeister (jon...@freebsd.org):

> Why are this certificates blacklisted?

Various reasons:
- Symantec (which owned Thawte and VeriSign back in the time) made
  the news in a bad way:
  https://www.theregister.com/2017/09/12/chrome_66_to_reject_symantec_certs/
- some certificates are simply expired
- some certificates use SHA-1 ("sha1WithRSAEncryption") which is
  beyond deprecated
- and basically "whatever Mozilla did", as the certificates are
  imported from NSS.

Regards,
Christoph

-- 
Spare Space
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Blacklisted certificates

[Jochen Neumeister]

Hi,

a make installworld stop with this:


>>> Installing everything completed on Wed Mar 31 11:45:55 CEST 2021
--
Scanning /usr/share/certs/blacklisted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Skipping blacklisted certificate 
/usr/share/certs/trusted/AddTrust_External_Root.pem 
(/etc/ssl/blacklisted/157753a5.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/AddTrust_Low-Value_Services_Root.pem 
(/etc/ssl/blacklisted/861a399d.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/EE_Certification_Centre_Root_CA.pem 
(/etc/ssl/blacklisted/128805a3.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/GeoTrust_Global_CA.pem 
(/etc/ssl/blacklisted/2c543cd1.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/GeoTrust_Primary_Certification_Authority.pem 
(/etc/ssl/blacklisted/480720ec.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/GeoTrust_Primary_Certification_Authority_-_G3.pem 
(/etc/ssl/blacklisted/e2799e36.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/GeoTrust_Universal_CA.pem 
(/etc/ssl/blacklisted/ad088e1d.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/GeoTrust_Universal_CA_2.pem 
(/etc/ssl/blacklisted/8867006a.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/LuxTrust_Global_Root_2.pem 
(/etc/ssl/blacklisted/def36a68.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/Staat_der_Nederlanden_Root_CA_-_G2.pem 
(/etc/ssl/blacklisted/5c44d531.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/Symantec_Class_1_Public_Primary_Certification_Authority_-_G4.pem 
(/etc/ssl/blacklisted/62744ee1.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/Symantec_Class_2_Public_Primary_Certification_Authority_-_G4.pem 
(/etc/ssl/blacklisted/4d4ba017.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/Taiwan_GRCA.pem (/etc/ssl/blacklisted/6410666e.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem 
(/etc/ssl/blacklisted/7d0b38bd.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem 
(/etc/ssl/blacklisted/b204d74a.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem 
(/etc/ssl/blacklisted/c0ff1f52.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/thawte_Primary_Root_CA.pem 
(/etc/ssl/blacklisted/2e4eed3c.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/thawte_Primary_Root_CA_-_G2.pem 
(/etc/ssl/blacklisted/c089bbbd.0)
Skipping blacklisted certificate 
/usr/share/certs/trusted/thawte_Primary_Root_CA_-_G3.pem 
(/etc/ssl/blacklisted/ba89ed3b.0)

Scanning /usr/local/share/certs for certificates...
root@joneumbox:/usr/src # uname -a
FreeBSD joneumbox.org 14.0-CURRENT FreeBSD 14.0-CURRENT #0 
main-51cc31088: Tue Mar 30 16:52:21 CEST 2021 
r...@joneumbox.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64



Why are this certificates blacklisted?


Greetings
Jochen

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: freebsd 13 ryzen micro stutter

[Alastair Hogge]

On 2021-03-28 16:09, Hans Petter Selasky wrote:
> On 3/27/21 11:54 AM, Santiago Martinez wrote:
>> Hi, i have the same output as @Nils B. If i run with steal =2 and dtrace the 
>> micro stutter doesn't happen but as soon as i stop the dtrace script it the 
>> stutters come back again.
>>
> 
> Here is a patch which you can try. Not sure if it helps.
> https://reviews.freebsd.org/D29467

Thanks Hans, this reduces jitter somewhat, but it still noticeable in
Quake2. I left kern.sched.steal_thresh at 1.

To good health,
Alastair.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: system freeze on 14.0-CURRENT,Re: system freeze on 14.0-CURRENT

[Masachika ISHIZUKA]

>>   I have trouble with recent 14.0-CURRENT 146 (e.x. main-6a762cfae,
>> main-3ead60236, main-25bfa4486).
>>   It works well on recent 14.0-CURRENT until starting firefox.
>>   If I start firefox (v87.0), system freeze but no core dumps.
>>   If it booted old kernel 145 (e.x. main-b5449c92b), firefox v87.0
>> is working well.
> 
> I have successful installed 14.0-CURRENT on the lenovo x1 carbon g8, but
> it just hangs when I tried to build the kernel. And I'm unable to enter
> the debugger. I think it happens when CPU load reaches some level.
> 
> I tried to disable hwpstate_intel via loader.conf and it helps:
> 
> % grep hint /boot/loader.conf
> hint.hwpstate_intel.0.disabled="1"

  Unfortunately, hint.hwpstate_intel.0.disabled="1" doesn't solve
XPS12 freeze problem.
-- 
Masachika ISHIZUKA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: system freeze on 14.0-CURRENT

[Andrey V. Elsukov]

28.03.2021 08:03, Masachika ISHIZUKA пишет:
>   I have trouble with recent 14.0-CURRENT 146 (e.x. main-6a762cfae,
> main-3ead60236, main-25bfa4486).
>   It works well on recent 14.0-CURRENT until starting firefox.
>   If I start firefox (v87.0), system freeze but no core dumps.
>   If it booted old kernel 145 (e.x. main-b5449c92b), firefox v87.0
> is working well.

I have successful installed 14.0-CURRENT on the lenovo x1 carbon g8, but
it just hangs when I tried to build the kernel. And I'm unable to enter
the debugger. I think it happens when CPU load reaches some level.

I tried to disable hwpstate_intel via loader.conf and it helps:

% grep hint /boot/loader.conf
hint.hwpstate_intel.0.disabled="1"

My old lenovo x1 carbon gen 4 was hanging on boot with the same symptoms.

-- 
WBR, Andrey V. Elsukov



OpenPGP_signature
Description: OpenPGP digital signature