similar to: [PATCH] ssh_config: reflect default CheckHostIP no

On 26 July 2018 at 15:52, Ed Maste <emaste at freebsd.org> wrote: > On 27 February 2018 at 09:06, Ed Maste <emaste at freebsd.org> wrote: >> >> A number of companies are shipping products based on FreeBSD/arm, on >> v5 and up. As far as I know those using older processors are also >> using older versions of FreeBSD (with a toolchain based on GCC and >>

On 26 July 2018 at 18:05, Ed Maste <emaste at freebsd.org> wrote: > On 26 July 2018 at 11:08, Peter Smith <peter.smith at linaro.org> wrote: >> On 26 July 2018 at 15:52, Ed Maste <emaste at freebsd.org> wrote: >>> On 27 February 2018 at 09:06, Ed Maste <emaste at freebsd.org> wrote: >>>> >>>> A number of companies are shipping

On 13 March 2018 at 16:51, Ed Maste <emaste at freebsd.org> wrote: > On 7 February 2018 at 01:20, Chandler Carruth via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> I've landed the patch in r324449. > > To confirm, this change *did not* make it into 6.0.0, correct? I'm > looking at adding the external thunk for FreeBSD now, and we have > 6.0.0 in

Does FreeBSD have fallocate(2) or equivalent? On Mon, Oct 30, 2017 at 4:32 PM, Ed Maste <emaste at freebsd.org> wrote: > On 23 October 2017 at 18:49, Rui Ueyama via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > >> > >> BTW, posix_fallocate() might provide better portability and decrease the > >> likelihood of falling back on ftruncate(). > >

On Fri, 11 Nov 2022 at 11:05, Ed Maste <emaste at freebsd.org> wrote: > > We had one more report from Coverity Scan after we brought 9.1p1 into > the FreeBSD base system. It complains that calls like "path1 = > make_absolute_pwd_glob(path1, *pwd);" in sftp.c leak the allocation. I see this same issue has since been reported by Coverity upstream and fixed in

On Tue, 29 Sep 2020 at 23:16, Nico Kadel-Garcia <nkadel at gmail.com> wrote: [...] > I gave up on $HOME/.ssh/known_hosts a *long* time ago, because if > servers are DHCP distributed without static IP addresses they can wind > up overlapping IP addresses with mismatched hostkeys You can set CheckHostIP=no in your config. As long as the names don't change it'll do what you

On Jan 19, 2017 2:48 AM, "Ed Maste" <emaste at freebsd.org> wrote: On 4 January 2017 at 13:34, Peter Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I'm about to start working on range extension thunks in lld. This is > an attempt to summarize the approach I'd like to take and what the > impact will be on lld outside of thunks. Now that LLD works

On Wed, Mar 15, 2017 at 6:02 PM, Ed Maste <emaste at freebsd.org> wrote: > Note that even if/when we get changes incorporated into libtool it > will still take a long time for the change to appear in new releases > of software packages using libtool. A downstream patch to the libtool > package in various operating systems or distributions doesn't really > help that much

On 28 October 2016 at 18:12, Ed Maste <emaste at freebsd.org> wrote: > It should be possible to search the path for ld.lld first, then ld, > but to me it seems like it will just be more confusing. Hum, for me it would be less confusing. :) GCC uses bfd by default, LLVM uses LLD. If you want to change, use -fuse-ld. What would be confusing in this scenario? > Clang's current

On Sun, 4 Oct 2020, Matthieu Herrb wrote: > Hi, > > on OpenBSD-current I now get this when connecting to an existing > machine for which I have both ecdsa an ed25519 keys in my existing > known_hosts (but apparently ed25519 keys where added only for the name > previsously by ssh): > > Warning: the ED25519 host key for 'freedom' differs from the key for > the

On Sun, Oct 04, 2020 at 09:24:12PM +1100, Damien Miller wrote: > On Sun, 4 Oct 2020, Damien Miller wrote: > > > No - I think you've stumbled on a corner case I hadn't anticipated. > > Does your configuration override CheckHostIP at all? No. > > > > What are the known_hosts entries for the hostname and IP? > > Also, do you use HashKnownHosts? or do

On 27 February 2018 at 05:29, Peter Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I've got some downstream patches > for v5 and v6 support (limit branch range, and use different > instructions in stubs), however I don't think anyone has actually > needed support yet. For FreeBSD we're on a path to having Clang + lld as our toolchain for all Tier-1

On Tue, 29 Sep 2020, Nico Kadel-Garcia wrote: > As I understand this option, it does not help at all with the nearly > inevitable re-use of the same IP address for a different host with a > different hostkey in, for example, a modest DHCP based environment. > Such environments are common both in smaller, private networks and in > large public networks, and it's perhaps

A change between r231216 and r231221 causes an assertion failure on the LLDB FreeBSD bot. The compiler is FreeBSD's in-tree one: FreeBSD clang version 3.5.1 (tags/RELEASE_351/final 225668) 20150115 First failing build: http://lab.llvm.org:8011/builders/lldb-x86_64-freebsd/builds/4668/steps/compile/logs/stdio Assertion: Assertion failed: ((!DD->isTrivial() ||

On 24 April 2015 at 16:32, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > > Until a git mirror is setup, we will need to use subversion ... What needs to happen in order to get the libunwind git mirror set up?

Hello, I've troubles getting the hostbased method to work. I've given up on system-to-system for now (different versions), and I'm just trying to debug localhost. As far as I can see, the key is accepted, but then a sudden "Failed hostbased" is returned: [...] debug3: mm_answer_keyallowed: key 0x8099bc0 is disallowed debug3: mm_append_debug: Appending debug messages for

Hi, I've found the option in CentOS 7 in sshd_config file #Host *.local # CheckHostIP no I think that option is for ssh_config, not for sshd_config. Please correct me if I'm wrong. Thanks in advance! -- -- Sergio Belkin http://www.sergiobelkin.com LPIC-2 Certified - http://www.lpi.org

On 13 August 2016 at 11:16, Davide Italiano via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > There's enough AArch64 to allow lld to self-host and to finish a build > of the base system on FreeBSD. Last we (I and Rafael) checked, it was > mid-june timeframe, but nothing changed since then. FYI when trying to link the FreeBSD/arm64 kernel now I receive tens of thousands of

On Wed, 22 Mar 2023 at 06:14, Ed Maste <emaste at freebsd.org> wrote: [...] > I see this same issue has since been reported by Coverity upstream and > fixed in 36c6c3eff5e4, but that change still missed all of the other > leaks addressed by my change. Applied, thanks. Interestingly our shiny new Coverity scan did not report any fixed leaks, though. -- Darren Tucker (dtucker at

On 27 May 2015 at 12:29, Justin Bogner <mail at justinbogner.com> wrote: > Mehdi Amini <mehdi.amini at apple.com> writes: >> Hi Manuel, >> >> I like Phabricator for code review much much more than emails. Let me know how >> I can help (I’m not afraid of PHP). > > Chandler updated the llvm phabricator doc to point at what we're deploying: > >