On Mon, Feb 24, 2020 at 3:56 PM Mario Olofo wrote:
> Hi Matt,
>
> The ext4 don't have data checksum, but have metadata checksum, which would
> probably be corrupted as well, as I reinstalled my Linux over the same
> partition the FreeBSD was using, and by
> now I have a lot more files on it than
On Mon, Feb 24, 2020 at 2:44 PM Mario Olofo wrote:
> Hi Pete, in the logs there's nothing wrong, I only see the problem on zpool
> status after the first scrub, even if I just
> reinstall the FreeBSD and some basic packages (didn't even need a lot of
> files as I thought).
Mario,
Out of curios
On Fri, Dec 27, 2019 at 12:10 PM Lee Damon wrote:
>
> Both times I observed this:
>
> : ldapsearch -v -LLL -x -h [redacted].ee.washington.edu -b
> dc=ee,dc=washington,dc=edu uid=[redacted]
> ldap_initialize( ldap://[redacted].ee.washington.edu )
> ldap_sasl_bind(SIMPLE): Can't contact LDAP server
her previous macOS version you were
using), and if so, were you encountering the same issue?
Thanks,
—
Matt Garber
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "
Try this instead, should be significantly faster at just displaying
snapshots without the sizing info (if that works for your use case):
# zfs list -t snapshot -o name -s name
Thanks,
—
Matt Garber
On Thu, Nov 14, 2019 at 9:34 AM mike tancsa wrote:
> We have a backup server that has a f
63170 ssh2
> Oct 18 10:35:35 ryzen-r12 sshd[63439]: debug1:
> /home/testuser1/.ssh/authorized_keys:2: matching key found: RSA
> SHA256:xx
I think it must be something that the server is trying even if the client
doesn’t actually send that type, since I also tested with OpenS
could think of, but unfortunately wasn’t able to determine which auth
type that log line corresponded to. It could also be an auth type that was
previously used, but sshd in 12.0-RELEASE re-ordered the processing sequence to
try it before public keys.
Thanks,
--
Matt Garber
___
ediate issue of getting blocked by sshguard before successfully processing
my key.)
Thanks,
--
Matt Garber
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Sun, May 19, 2019 at 9:00 AM Scott Bennett wrote:
>
> Many, many thanks to the person who responded with the solution to
> get past the
> loader crash!! My system is now getting work done again, and the rest of
> the new
> problems can be dealt with on a running system.
Out of curiosit
On Wed, May 15, 2019 at 11:15 PM Bill Sorenson
wrote:
> > I’m not sure what you meant about Linux distros not categorizing fixes,
> though — with some notable exceptions, most of the big ones certainly tag
> security fixes >separately, which is what allows `unattended-upgrades` on
> Debian/Ubuntu
On Wed, May 15, 2019 at 10:28 PM Bill Sorenson
wrote:
> > Admins attentive to security issues will already be tracking CVEs for
> > the software they use and mitigating or solving the vulnerability by all
> > means available.
> >
> > By batching updates, FreeBSD is making administrative decisions
> On May 15, 2019, at 12:28 PM, Andrea Venturoli wrote:
>
> On 5/15/19 6:16 PM, Matt Garber wrote:
>
>> Exactly. If batching 8 (or more) individual bugs/issues together into
>> one release is really causing admin/manpower overload and angst,then
>> maybe it’s tim
ems like it would
be related to how else you’re handling the upgrade process(es), not whether the
fixes are batched or not. Whatever other negative things you can say about
them, I don’t hear enterprise admins begging that Microsoft/Oracle/whoever
would dribble out patches one at a time each
ion you have installed via
packages/ports/etc.
Thanks,
—
Matt Garber
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
mpiling-and-installing-modsecurity-for-open-source-nginx/>,
after taking care of the prerequisites with FreeBSD packages instead. Like I
said, you could probably relatively easily hack the nginx port to add in the
integration of ModSecurity3-nginx if you care about that more than keeping
d | grep security
ap24-mod_security-2.9.2_3 Intrusion detection and prevention engine
modsecurity3-3.0.3_1 Intrusion detection and prevention engine
Thanks,
—
Matt Garber
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
protocol for exactly the scenario
you’re describing; I’ve heard it’s very straightforward and powerful to use,
although haven’t had to use it on any of my HAProxy instances which are
primarily doing L7.
https://www.haproxy.com/blog/preserve-source-ip-address-despite-reverse
ing a giant shell script which you can
use on fresh instances, so you’re not having to re-edit config. files by hand
each time.
--
Matt Garber
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsub
be fine. If you’re still nervous, just snapshot your
boot EBS volume first as an extra precautionary measure, and destroy it once
you verify everything post-upgrade.
--
Matt Garber
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/
another CC prior to upgrading to
12.0-RELEASE/STABLE, or they should wait until the Errata Notice is
hopefully released with the reverted change. Otherwise they'll encounter
the same network connection stalls and problems.
--
Thanks,
-Matt Garber
_
an Errata Notice will hopefully be published at some point
in January after the holidays.
Hope this saves some troubleshooting!
—
Thanks,
-Matt Garber
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd
21 matches
Mail list logo
