[Bug 198941] After setting with tzsetup non-UTC Finland/Helsinki EET, clock is off +1 hours

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198941

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
   Assignee|b...@freebsd.org|go...@freebsd.org

--- Comment #1 from Oleksandr Tymoshenko  ---
Hello Juha,

Is this issue still valid for currently supported versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 208892] Remove Busingen from tzsetup

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208892

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
 Status|New |Closed
 Resolution|--- |Not A Bug

--- Comment #1 from Oleksandr Tymoshenko  ---
tzsetup operates on the list of zones from tzdata, 3rd-party library/dataset,
FreeBSD uses it as-is, without modifications. Apparently at some point DST
rules in Busingen and DD/DE were different which by tzdata rules warrants
creating dedicated record for it:

https://github.com/eggert/tz/blob/master/europe#L1422

# From Tobias Conradi (2011-09-12):
# Büsingen , surrounded by the Swiss canton
# Schaffhausen, did not start observing DST in 1980 as the rest of DE
# (West Germany at that time) and DD (East Germany at that time) did.
# DD merged into DE, the area is currently covered by code DE in ISO 3166-1,
# which in turn is covered by the zone Europe/Berlin.
#
# Source for the time in Büsingen 1980:
# http://www.srf.ch/player/video?id=c012c029-03b7-4c2b-9164-aa5902cd58d3

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234990] Samsung 860 EVO 2TB SSD does not work with Supermicro 10DRT-PTR

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234990

Bug ID: 234990
   Summary: Samsung 860 EVO 2TB SSD does not work with Supermicro
10DRT-PTR
   Product: Base System
   Version: 12.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: cra...@monkeybrains.net

Incompatible combo: Samsung SSD EVO 860 2TB SSD / 2TB with SuperMicro 10DRT-PTR
board


Workaround:
Disable TRIM.  You can do this on a system showing symptoms by running this
command (takes 10 seconds to complete):

echo vfs.zfs.trim.enabled=0 >> /boot/loader.conf && reboot

Workaround during install:

Also, if you are installing from MEMSTICK and cannot create the ZFS pool due to
errors, you can disable TRIM and reboot memstick.

[1] During installation, open terminal by typing: ALT-F4.
[2] Mount the USB stick rw:  mount -u -o rw /
[3] and then edit the loader.conf on the USB stick:
echo vfs.zfs.trim.enabled=0 >> /boot/loader.conf && reboot


Info on disks:

# camcontrol devlist
  at scbus5 target 0 lun 0 (pass1,ada0)
  at scbus6 target 0 lun 0 (pass2,ada1)

Info on Motherboard from dmidecode:
   Supermicro, X10DRT-PTR


Errors logs:

Jan 15 07:23:31 dosa-b kernel: ahcich4: Timeout on slot 7 port 0
Jan 15 07:23:31 dosa-b kernel: ahcich4: is  cs  ss  rs
0080 tfd 40 serr  cmd 0004c717
Jan 15 07:23:31 dosa-b kernel: (ada0:ahcich4:0:0:0): SEND_FPDMA_QUEUED DATA SET
MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00
Jan 15 07:23:31 dosa-b kernel: ahcich5: (ada0:ahcich4:0:0:0): CAM status:
Command timeout
Jan 15 07:23:31 dosa-b kernel: (ada0:ahcich4:0:0:0): Retrying command, 3 more
tries remain
Jan 15 07:23:31 dosa-b kernel: Timeout on slot 8 port 0
Jan 15 07:23:31 dosa-b kernel: ahcich5: is  cs  ss  rs
0100 tfd 40 serr  cmd 0004c817
Jan 15 07:23:31 dosa-b kernel: (ada1:ahcich5:0:0:0): SEND_FPDMA_QUEUED DATA SET
MANAGEMENT. ACB: 64 01 00 00 00 40 00 00 00 00 00 00
Jan 15 07:23:31 dosa-b kernel: (ada1:ahcich5:0:0:0): CAM status: Command
timeout
Jan 15 07:23:31 dosa-b kernel: (ada1:ahcich5:0:0:0): Retrying command, 3 more
tries remain

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234965] scp client multiple vulnerabilities (openssh in base/ports affected: CVE-2018-20685 CVE-2019-6111 CVE-2019-6109,6110)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234965

Kubilay Kocak  changed:

   What|Removed |Added

 Status|New |Open
   Priority|--- |Normal
   Assignee|b...@freebsd.org|ports-sect...@freebsd.org
Summary|openssh, scp vulnerability  |scp client multiple
   |CVE-2018-20685  |vulnerabilities (openssh in
   |CVE-2019-6111   |base/ports affected:
   |CVE-2019-6109,6110  |CVE-2018-20685
   ||CVE-2019-6111
   ||CVE-2019-6109,6110)
 CC||bdrew...@freebsd.org,
   ||ema...@freebsd.org,
   ||ports-sect...@freebsd.org
URL||https://sintonen.fi/advisor
   ||ies/scp-client-multiple-vul
   ||nerabilities.txt

--- Comment #2 from Kubilay Kocak  ---
base r343043 by emaste@ addressed one of the issues (CVE-2018-20685)

CC bdrewery (security/openssh-portable maintainer)

According to the article/announcement details, openssh is vulnerable to all
four CVE's.

I'd use this as a parent coordinator issue, with separate sub issues created
for each of base openssh and ports openssh being tracked separately for clarity
of merges (base issues only multiple MFC flags, ports issues have a single
merge quarterly flag), and given base and ports components have different
maintainers.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234987] clang 6.0.1 coredump on gtk-gnutella

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234987

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|toolch...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234156] OpenSSL partially not working

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234156

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|New |Closed
 CC||go...@freebsd.org
 Resolution|--- |Not A Bug

--- Comment #2 from Oleksandr Tymoshenko  ---
This is intended behavior at the moment, trusted CA certificates are not
shipped in base OS and have to be installed separately.

Mailing list (freebsd-hacker or freebsd-arch or freebsd-current) is probably a
better places for discussing possible alternatives for this policy.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 231354] Potential null pointer deference in drm/r128

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231354

--- Comment #2 from Young  ---
See https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3620 and
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7dc482dffcfd000d4271c4626937406756d7
for detail.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 202298] usr/src/sys/dev/beri/virtio/virtio_block.c:404: 21 into 20 won't go

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202298

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
   Assignee|b...@freebsd.org|go...@freebsd.org
   See Also||https://reviews.freebsd.org
   ||/D18852
 Status|New |In Progress

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234987] clang 6.0.1 coredump on gtk-gnutella

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234987

Jamie Landeg-Jones  changed:

   What|Removed |Added

 CC||ja...@catflap.org
   Hardware|Any |amd64

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234987] clang 6.0.1 coredump on gtk-gnutella

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234987

Bug ID: 234987
   Summary: clang 6.0.1 coredump on gtk-gnutella
   Product: Base System
   Version: 12.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: ja...@catflap.org

Created attachment 201175
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201175=edit
thread-3519b5.tar.xz contains the preprocessed source and associated run script

FreeBSD/amd64 12.0-STABLE - Build 1200501 (Jan 07, 2019)

+ cc -c -I../.. -I.. -I/usr/local/include/glib-2.0
-I/usr/local/lib/glib-2.0/include -I/usr/local/include -pthread
'-DCURDIR=src/lib' -O2 -pipe '-march=native' '-mtune=native' -ftree-vectorize
-DLIBICONV_PLUG -fstack-protector -isystem /usr/local/include
-fno-strict-aliasing -pthread -momit-leaf-frame-pointer -W -Wall '-Wformat=2'
-Wshadow -DLIBICONV_PLUG -isystem /usr/local/include thread.c
cc: error: unable to execute command: Segmentation fault (core dumped)
cc: error: clang frontend command failed due to signal (use -v to see
invocation)
FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM
6.0.1)
Target: x86_64-unknown-freebsd12.0
Thread model: posix
InstalledDir: /usr/bin
cc: note: diagnostic msg: PLEASE submit a bug report to
https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed
source, and associated run script.
cc: note: diagnostic msg:


PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
cc: note: diagnostic msg: /temp/root/thread-3519b5.c
cc: note: diagnostic msg: /temp/root/thread-3519b5.sh
cc: note: diagnostic msg:



There was no meaningful backtrace (I assume because clang is stripped)
preprocessed source and run script attached (tar.xz)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234838] ena drop-outs on 12.0-RELEASE

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234838

--- Comment #4 from Colin Percival  ---
(In reply to Leif Pedersen from comment #3)

Can you build a kernel with the patch from r343071?  Apparently the 'failed to
prepare tx bufs' situation is harmless (and the message should only be printed
when debugging is turned on) but it's possible that the mere act of logging the
warning is causing timeouts -- so it would be good to know if you see any sign
of the device resets after applying this patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 205721] usr/src/sys/mips/rt305x/rt305x_spi.c:250: possible missing break ?

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205721

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Overcome By Events
 CC||go...@freebsd.org

--- Comment #2 from Oleksandr Tymoshenko  ---
The file was deleted as part of base r327457 (unifying Mediatek code under
sys/mips/mediatek)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234985] kernel panic when destroying epair interface of vnet jail after using ifconfig inside the jail

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985

--- Comment #2 from Henno Schooljan  ---
Interesting fact after doing some more testing: All is well also when I do not
remove the jails, or when I remove the jail *after* destroying the epair
interface.

Only when I remove the jail *before* destroying the epair interface *and* I run
the ifconfig command inside the jail, I can trigger the panic.

I hope I provided enough info, let me know if I can test and/or provide
anything else to pinpoint the issue here.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234985] kernel panic when destroying epair interface of vnet jail after using ifconfig inside the jail

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985

--- Comment #1 from Henno Schooljan  ---
Created attachment 201174
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201174=edit
trace_13.0-CURRENT-r343065.txt: kernel trace

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234985] kernel panic when destroying epair interface of vnet jail after using ifconfig inside the jail

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234985

Bug ID: 234985
   Summary: kernel panic when destroying epair interface of vnet
jail after using ifconfig inside the jail
   Product: Base System
   Version: CURRENT
  Hardware: amd64
OS: Any
Status: New
  Keywords: panic, vimage
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: he...@schooljan.nl

Created attachment 201173
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201173=edit
vnet_epair_test.sh: Script for reproducing vnet jail epair destroy panic

When creating an epair interface pair for a VNET enabled jail, and then using
ifconfig within this jail, the kernel will often panic later when destroying
the jail and finally the epair interface again. However this will not happen
when ifconfig is not used within the jail or when it is used outside of the
jail, and it will not happen every time. But when it happens, it always happens
at the moment the ifconfig destroy epair is done.

This has been tested and reproduced on 12.0-RELEASE-p2 and 13.0-CURRENT
r343065.

I have included a script which reproduces this. It is based on an older script
which tested for a similar issue, and I changed it so that it will test this
999 times, with an optional 'panic' argument for triggering the critical
ifconfig command that makes the difference here.
With the panic argument it will reliably panic my system on every run, at worst
after a couple hundred loops or so (perhaps it is some kind of race
condition?). Without the panic argument the system never crashes.

I have also included the kernel trace I obtained from the 13.0-CURRENT system,
and can supply a kernel memory dump if you need it.

So what side effect would this innocent ifconfig command have that it affects a
later ifconfig destroy command? It also does not matter which interface you
query with it, like when you run ifconfig lo0 or something else, as long as I
use ifconfig at least once I can trigger this.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 201593] usr/src/sys/dev/iicbus/max6690.c:372: poor error checking ?

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201593

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||go...@freebsd.org
 Status|New |Closed

--- Comment #1 from Oleksandr Tymoshenko  ---
Thanks for reporting. The fix was committed as base r259080.

Closing as fixed

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 206754] Out of bounds negative array index in iicrdwr

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206754

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
 Status|Open|Closed
   See Also||https://reviews.freebsd.org
   ||/D5155
 Resolution|--- |FIXED

--- Comment #9 from Oleksandr Tymoshenko  ---
The fix was committed as base r300258. Closing as Fixed

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 216477] cannot build kernel with gpio devices

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216477

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Unable to Reproduce
 CC||go...@freebsd.org

--- Comment #1 from Oleksandr Tymoshenko  ---
Thanks for reporting.

There is no reference of to "gpioc" device in the gpioiic(4) man page, so I
believe it was a mistake when adding the config snippet. I copy-pasted  man
page to tools/tools/nanobsd/pcengines/ALIX_DSK and used it as a kernel config,
the build went fine on HEAD and stable/11.

Closing as "Unable to Reproduce"

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 207786] gpioiic_callback() dereferences IIC "how" argument incorrectly

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207786

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|New |Closed
   Assignee|b...@freebsd.org|go...@freebsd.org
 Resolution|--- |FIXED

--- Comment #5 from Oleksandr Tymoshenko  ---
Closing as the submitted patch was committed in base r297794.

Thanks for reporting.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 226575] drill -x 192..168.5.25 (two dots in the row) breaks

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226575

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|New |In Progress
   Assignee|b...@freebsd.org|go...@freebsd.org
 CC||go...@freebsd.org

--- Comment #3 from Oleksandr Tymoshenko  ---
Drill is a contrib code. I forwarded  report to the upstream bugzilla:
https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4221

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 231513] off-by-one overflow in drm_ioctl (sys/dev/drm/drm_drv.c)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231513

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
 Status|New |Closed
 Resolution|--- |FIXED
   Assignee|b...@freebsd.org|go...@freebsd.org

--- Comment #4 from Oleksandr Tymoshenko  ---
Thanks for submitting the patch. Committed as base r343060, I'll handle MFC in
a week.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 231513] off-by-one overflow in drm_ioctl (sys/dev/drm/drm_drv.c)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231513

--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:

Author: gonzo
Date: Tue Jan 15 21:06:59 UTC 2019
New revision: 343060
URL: https://svnweb.freebsd.org/changeset/base/343060

Log:
  [drm] Fix off-by-one error when accessing driver-specific ioctl handlers
array

  PR:   231513
  Submitted by: Young_X 
  Approved by:  imp
  MFC after:1 week

Changes:
  head/sys/dev/drm/drm_drv.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 220623] [patch] makewhatis crashes if a manpage has .ce active

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220623

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|New |Closed
   Assignee|b...@freebsd.org|go...@freebsd.org
 Resolution|--- |Overcome By Events
 CC||go...@freebsd.org

--- Comment #3 from Oleksandr Tymoshenko  ---
Thanks for submitting the patch and test case. This is fixed in 11.2 and 12.0
so it must have been fixed in upstream. Closing as OBE.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 233413] lld does not accept -format arg used by lazarus build system

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233413

--- Comment #6 from commit-h...@freebsd.org ---
A commit references this bug:

Author: thierry
Date: Tue Jan 15 20:52:34 UTC 2019
New revision: 490402
URL: https://svnweb.freebsd.org/changeset/ports/490402

Log:
  Set LLD_UNSAFE.

  PR:   233413
  Reported by:  emaste

Changes:
  head/multimedia/winff/Makefile

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 231513] off-by-one overflow in drm_ioctl (sys/dev/drm/drm_drv.c)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231513

Warner Losh  changed:

   What|Removed |Added

 CC||i...@freebsd.org

--- Comment #2 from Warner Losh  ---
I think this is good.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234972] yppasswdd cannot update passwd (rename of /var/yp to /var/yp/master. passwd.hold failed)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234972

Mark Linimon  changed:

   What|Removed |Added

   Keywords||regression

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234975] CLI issue with grep and width of terminal

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234975

--- Comment #4 from C Haas  ---
the -ww worked like a charm.  Thank you.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234975] CLI issue with grep and width of terminal

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234975

Deepak Nagaraj  changed:

   What|Removed |Added

 CC||n.dee...@gmail.com

--- Comment #3 from Deepak Nagaraj  ---
Hi Conrad, the fix was restored with a bit of change:
https://svnweb.freebsd.org/changeset/base/330712

Does this not apply to all later versions of FreeBSD?

Thanks,
Deepak

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234975] CLI issue with grep and width of terminal

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234975

Conrad Meyer  changed:

   What|Removed |Added

 Status|New |Closed
 CC||kar...@freebsd.org
 Resolution|--- |DUPLICATE

--- Comment #2 from Conrad Meyer  ---
This is an old bug and attempts to fix it after 11.x were reverted by karels@
r330091.  You'll need to add the '-ww' flags to ps to get it to ignore terminal
width.

*** This bug has been marked as a duplicate of bug 217159 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234976] Clang: undefined reference to __atomic_exchange and __atomic_load

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234976

Mark Linimon  changed:

   What|Removed |Added

  Component|misc|bin
   Assignee|b...@freebsd.org|toolch...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 219846] [panic] [kevent] mutex nm_kn_lock not owned, netmap with INVARIANTS+WITNESS

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219846

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234976] Clang: undefined reference to __atomic_exchange and __atomic_load

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234976

Bug ID: 234976
   Summary: Clang: undefined reference to __atomic_exchange and
__atomic_load
   Product: Base System
   Version: 12.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: vallen...@icir.org

I'm having trouble with compiling the following code snippet:

#include 
#include 

struct sixteen {
  uint64_t x = 1;
  int64_t  y = -1;
};

std::atomic x;

int main() {
  auto v = x.load(std::memory_order_relaxed);
  return std::atomic_is_lock_free();
}

I've attempted to compile this as follows:

c++ -std=c++17 -stdlib=libc++ test.cpp
/tmp/test-3fe722.o: In function `main':
test.cpp:(.text+0x34): undefined reference to `__atomic_load'
test.cpp:(.text+0x86): undefined reference to `__atomic_is_lock_free'
c++: error: linker command failed with exit code 1 (use -v to see invocation)

The same snippet compiles fine with GCC 8 and -latomic.

This issue appears to be related to bug #233725 and bug #220822.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234975] CLI issue with grep and width of terminal

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234975

--- Comment #1 from C Haas  ---
Forgot to mention, I tried many terminal clients (putty, mintty, vmware fusion
guest window) and all had the same issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234975] CLI issue with grep and width of terminal

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234975

Bug ID: 234975
   Summary: CLI issue with grep and width of terminal
   Product: Base System
   Version: 11.2-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: haasca2...@gmail.com

Discovered an issue where if you are grepping for a string that falls outside
of the window size, the line is not found.  For example, I was running
11.2-stable in a VM and ssh'ing into it from a MAC and only had a window up
that was 80 char wide.  The `ps -aux` returned a string for a java program I
was running that was well over 80 chars and the string i was searching for fell
after the 80 char boundary.  that line was not returned in the grep search.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234965] openssh, scp vulnerability CVE-2018-20685 CVE-2019-6111 CVE-2019-6109,6110

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234965

Kyle Evans  changed:

   What|Removed |Added

 CC||kev...@freebsd.org,
   ||sect...@freebsd.org

--- Comment #1 from Kyle Evans  ---
CC'ING secteam, perhaps

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234968] syslogd remote logging doesn't work (regression ?)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234968

--- Comment #2 from Julien Cigar  ---
maybe related to base r332110

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234972] yppasswdd cannot update passwd (rename of /var/yp to /var/yp/master. passwd.hold failed)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234972

Bug ID: 234972
   Summary: yppasswdd cannot update passwd (rename of /var/yp to
/var/yp/master. passwd.hold failed)
   Product: Base System
   Version: 12.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: bernard.marsh...@axiell.com

After upgrading to 12.0 RELEASE the yppasswdd RPC no longer updates passwords
successfully. When trying to update a password the following is output:

$ passwd fred
Changing NIS password for fred
New Password:
Retype New Password:
passwd: pam_chauthtok(): Error in service module

A check of /var/log/messages shows one of the following errors depending on
whether the -t option was set for nis_yppasswdd_flags in /etc/rc.conf:

rename of / to /.hold failed
rename of /var to /var/yp.hold failed
rename of /var/yp to /var/yp/master.passwd.hold failed

The error is in /usr/src/usr.sbin/rpc.yppasswdd/yppasswdd_server.c where
dirname() is used twice (line 609 and 832). Both lines have the code:

if (pw_init(dirname(passfile), passfile)) {

It looks like the implementation of dirname in 12.0 RELEASE has changed to now
apply changes to the string passed into the function. The change is to make the
call thread safe according to the updated manual entry. The problem here is
that the call to dirname() now truncates "passfile" meaning the variable no
longer holds the path to the master password file, rather just the directory
and hence the error.

In order to use dirname() now "passfile" will need to be copied before being
passed into dirname().

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234968] syslogd remote logging doesn't work (regression ?)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234968

--- Comment #1 from Julien Cigar  ---
Ok I found the issue, it works if I'm removing the local domain part (router1
instead of router1.lan) although both "router1" and "router1.lan" return the
same ip address (10.209.1.252):


WORKS:

root@logging:~ # cat /usr/local/etc/syslog.d/saltstack.conf 
+router1,router2,router
local6.=info/var/log/haproxy/http-access.log
local6.=err /var/log/haproxy/http-error.log
local5.*/var/log/haproxy/smtp.log

DOESN'T WORK:

root@logging:~ # cat /usr/local/etc/syslog.d/saltstack.conf 
+router1.lan,router2.lan,router.lan
local6.=info/var/log/haproxy/http-access.log
local6.=err /var/log/haproxy/http-error.log
local5.*/var/log/haproxy/smtp.log

root@logging:/var/log/haproxy # host router1
router1.lan has address 10.209.1.252
root@logging:/var/log/haproxy # host router1.lan
router1.lan has address 10.209.1.252
root@logging:/var/log/haproxy # host 10.209.1.252
252.1.209.10.in-addr.arpa domain name pointer router1.lan.

is it an expected behavior ? if yes feel free to close it, but I think it
should be mentioned somewhere in the syslogd manpage.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234968] syslogd remote logging doesn't work (regression ?)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234968

Julien Cigar  changed:

   What|Removed |Added

  Component|kern|bin

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234969] ctladm: assertion fails in function nvlist_destroy

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234969

Bug ID: 234969
   Summary: ctladm: assertion fails in function nvlist_destroy
   Product: Base System
   Version: 12.0-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: kukub...@go2.pl

Created attachment 201160
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201160=edit
coredump

When configuring fibre channel target ctladm coredumps.

# ctladm port -o on -t fc

Front End Ports enabled

Assertion failed: ((nvl)->nvl_magic == 0x6e766c), function nvlist_destroy, file
/usr/src/sys/contrib/libnv/nvlist.c, line 158.

Abort trap (core dumped)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234968] syslogd remote logging doesn't work (regression ?)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234968

Julien Cigar  changed:

   What|Removed |Added

Summary|syslogd remote logging  |syslogd remote logging
   |doens't work (regression ?) |doesn't work (regression ?)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234968] syslogd remote logging doens't work (regression ?)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234968

Bug ID: 234968
   Summary: syslogd remote logging doens't work (regression ?)
   Product: Base System
   Version: 12.0-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: jul...@perdition.city

Created attachment 201159
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201159=edit
logging jail syslogd

Hello,

I have a JAIL (logging, 10.209.1.31) which is used as a centralized log host.
The JAIL and the HOST are running FreeBSD 12.0-RELEASE.

The JAIL has an unmodified syslog.conf with one extra file in
/usr/local/etc/syslog.d:

root@logging:~ # ls -l /usr/local/etc/syslog.d
total 5
-rw-r--r--  1 root  wheel  312 Jan 15 10:45 saltstack.conf

root@logging:~ # cat /usr/local/etc/syslog.d/saltstack.conf 
+router1.lan,router2.lan,router.lan
local6.=info/var/log/haproxy/http-access.log
local6.=err /var/log/haproxy/http-error.log
local5.*/var/log/haproxy/smtp.log
+dev.lan,antabif.lan,gitlab.lan,sandbox.lan,www1.prod.lan,www2.prod.lan
local6.=info/var/log/httpd/access.log
local6.=err /var/log/httpd/error.log

DNS and reverse DNS are working properly. If I'm tcpdumping on the HOST
everything look OK, packets are properly sent from remote hosts:

root@HOST:~/ sudo tcpdump -n -i bge0 -p udp port 514 and host logging.lan
Password:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bge0, link-type EN10MB (Ethernet), capture size 262144 bytes
11:31:37.273760 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 207
11:31:37.501015 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 208
11:31:38.074736 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local5.info,
length: 151
11:31:38.501954 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 208
11:31:38.504479 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 205
11:31:38.586405 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 207
11:31:38.943227 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local5.info,
length: 151
11:31:39.378678 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 177
11:31:39.500904 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 208
11:31:39.680232 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 177
11:31:39.694193 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 219
11:31:39.906661 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local5.info,
length: 151
11:31:40.134680 IP 192.168.10.34.514 > 10.209.1.31.514: SYSLOG local6.error,
length: 246
11:31:40.276486 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 207
11:31:40.494038 IP 192.168.10.34.514 > 10.209.1.31.514: SYSLOG local6.error,
length: 246
11:31:40.501695 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 208
11:31:40.612300 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 241
11:31:40.745679 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info,
length: 236
(...)

I've launched syslogd in debug mode in the JAIL and as you can see syslog
messages arrive properly to the syslogd (see attachment). For some unknown
reasons nothing gets logged to /var/log/haproxy/*.log

DNS and reverse DNS are working properly:

root@logging:~ # host 10.209.1.252
252.1.209.10.in-addr.arpa domain name pointer router1.lan.

root@logging:~ # host router1.lan
router1.lan has address 10.209.1.252

syslogd on the HOST is binded to the HOST ip, files exist in /var/log/haproxy
in the JAIL, etc:

root@logging:~ # ls -l /var/log/haproxy/
total 2
-rw---  1 root  wheel  0 Jan 15 10:48 http-access.log
-rw---  1 root  wheel  0 Jan 15 10:48 http-error.log
-rw---  1 root  wheel  0 Jan 15 10:48 smtp.log

Note that the same config worked in 10.4-RELEASE as expected and I'm out of
ideas why it doesn't work on 12.0-RELEASE

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234965] openssh, scp vulnerability CVE-2018-20685 CVE-2019-6111 CVE-2019-6109,6110

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234965

Bug ID: 234965
   Summary: openssh, scp vulnerability CVE-2018-20685
CVE-2019-6111 CVE-2019-6109,6110
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: security
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: b...@mrp3.com

according to this article:

https://www.theregister.co.uk/2019/01/15/scp_vulnerability/

OpenSSH 7.9 and earlier contain a set of vulnerabilities that date back to
1983.

These are:

CVE-2018-20685 - server can alter directory permissions on the client

CVE-2019-6111 -  server can send arbitrary files not requested by the client,
even overwriting files in the client's file system.

CVE-2019-6109, CVE-2019-6110 - server can alter the object name or output
display on the ssh client to hide files being copied


There is apparently a patch available, linked to from the article mentioned
above, which appears to apply to -CURRENT from a few days ago.  I have not
attempted to build the source.  however, the patch is available here:

https://sintonen.fi/advisories/scp-name-validator.patch

Since I have only verified that the code in the FreeBSD crypto/openssh tree
does not appear to have been patched for these vulnerabilities, I can not for
certain say that they exist; however, it is extremely likely and needs to be
brought to the attention of the appropriate people.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234962] Base64 Encoding in phttpget is faulty

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234962

kopplow@gmail.com changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=1532
   ||11

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234962] Base64 Encoding in phttpget is faulty

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234962

kopplow@gmail.com changed:

   What|Removed |Added

 CC||kopplow@gmail.com
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=1294
   ||31

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 234962] Base64 Encoding in phttpget is faulty

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234962

Bug ID: 234962
   Summary: Base64 Encoding in phttpget is faulty
   Product: Base System
   Version: 12.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: kopplow@gmail.com

This issue breaks freebsd-update for proxy users who needs to authenticate with
username and password and have username:password combinations which are in not
a multiple of 3 in combined length.

Due to an issue with the Base64 Filling which is not applied correctly many
username:password combinations provided via the HTTP_PROXY_AUTH Environment
Variable are not encoded correctly for the use of the HTTP Proxy-Authentication
Header.

Replicability should be 100% and this issue seem to exists since Version 7
already and is really annoying.

I compiled a version of phttpget with an alternate Base64 Encoding
Implementation to confirm this issue and got it to work.

Test Scenario:

- Environment: System needs to be behind Proxy Server with Authentication

 - Set HTTP_PROXY_AUTH to "basic:*:Hey:Base64!!" (Username:Password portion is
12 Characters long)
 - run /usr/libexec/phttpget to download any file
 - Download should work since the "Hey:Base64!!" is 12 Chars in total which
doesn't require Base64 to fill with "=" chars.
 - Set HTTP_PROXY_AUTH to "basic:*:Hey:Base64" (Username:Password portion is 10
Characters long)
 - Download shouldn't work since the filling is getting applied wrong and
results in "SGV5OkJhc2U2NAA=" which is not correct.

Possible related issues:
 - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129431
 - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=153211

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"