similar to: Host selection in ssh_config

Hi all. Funny thing happend: I had winbindd working, but now I can't get it back up correctly. I'm not sure what I'm doing differently. Samba version 2.2.5. 'wbinfo -u' says "Error looking up domain users". I joined the domain with the command: 'smbpasswd -j OUR_DOMAIN -r thepdc -U Administrator' and this returned saying "Joined domain

https://bugzilla.mindrot.org/show_bug.cgi?id=2731 Bug ID: 2731 Summary: .ssh/config: Host * overrides included files Product: Portable OpenSSH Version: 7.5p1 Hardware: amd64 OS: Linux Status: NEW Severity: trivial Priority: P5 Component: ssh Assignee: unassigned-bugs at

Hi all, Here there are trust relationship between domains. On some file server using Samba 4.4.4 (Centos 7) I must set up my shares using %U. When using %u the directory which is accessed is /path/to/share/OUR_DOMAIN\username rather than /path/to/share/username. Initially I thought it could be solved by using: winbind use default domain = yes associated with: workgroup = OUR_DOMAIN but that

Brian Candler wrote: > Chris Green wrote: > > ... redundant ones are because I have a mixed population of > > Raspberry Pis and such on my LAN and they get rebuilt fairly > > frequently and thus, each time, get a new entry in known_hosts. > ...many useful tips... > To disable host key checking altogether for certain domains and/or networks, > you can put this in

Hi All, I'm using samba 3.0.10-1 on RedHat Enterprise Linux 4. I'm authentication to our PDC using Winbind and also mounting our home directory share (from Windows) onto our main Linux server such that when a user logs on to the Linux server, their Windows home directory is mounted also. I'm using the domain admin account to mount the home directory share, which I feel is

2017-08-31 15:54 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: > On Thu, 31 Aug 2017 15:28:57 +0200 > mathias dufresne via samba <samba at lists.samba.org> wrote: > > > Hi all, > > > > Here there are trust relationship between domains. > > On some file server using Samba 4.4.4 (Centos 7) I must set up my > > shares using %U. When

On Mon, Oct 14, 2024 at 5:33?AM Jan Eden via openssh-unix-dev <openssh-unix-dev at mindrot.org> wrote: redacted hostname and port ? sorry, should have mentioned that. > > > Anyway, in answer to your question. The "host key found matching a different > > name/address" is triggered when a key received from the server in an update > > already exists under a

Hello all, I inherited a Samba4 domain controller also acting as DNS and unfortunately this is all new to me. Asking the DNS for the content of a certain zone with # samba-tool dns query ip_of_domain_controller name_of_zone @ ALL -U administrator brings up two entries that look different. A good and working entry looks like this: Name=1, Records=1, Children=0 PTR: pcname.our_domain.local

On 14/02/2024 11:42, Chris Green wrote: > Is there any way to remove old entries from the known_hosts file? With > the hashed 'names' one can't easily see which entries are which. I > have around 150 lines in my known hosts but in reality I only ssh to a > dozen or so systems. All the redundant ones are because I have a > mixed population of Raspberry Pis and such on

Perfect, thanks. This winds up working for me (as far as I've tested so far.) Match exec "ping -q -c 1 -t 1 %n | grep '192\.168\.'" StrictHostKeyChecking no UserKnownHostsFile none On Wed, Aug 26, 2015 at 11:47 PM, Bostjan Skufca <bostjan at a2o.si> wrote: > (+cc list) > > You could use something in the following manner: > > Match originalhost *

2017-08-31 16:29 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: > On Thu, 31 Aug 2017 16:08:00 +0200 > mathias dufresne <infractory at gmail.com> wrote: > > > 2017-08-31 15:54 GMT+02:00 Rowland Penny via samba > > <samba at lists.samba.org>: > > > > > On Thu, 31 Aug 2017 15:28:57 +0200 > > > mathias dufresne via samba

If I want to specify for LAN addresses that I don't want to deal with host keys, how do I do that? Understanding the risks, knowing almost everyone will say not to do this - it's a horrible idea, but deciding I want to do it anyway. Tired of having to remove entries from known_hosts with the multiple VM's I have that often change fingerprints, and am willing to live with the risks.

On Fri, Aug 28, 2015 at 11:51 PM, Walter Carlson <wlcrls47 at gmail.com> wrote: > On Thu, Aug 27, 2015 at 12:26 AM, Walter Carlson <wlcrls47 at gmail.com> wrote: > >> Perfect, thanks. This winds up working for me (as far as I've tested so >> far.) >> >> Match exec "ping -q -c 1 -t 1 %n | grep '192\.168\.'" >>

On Sun, 4 Oct 2020, Christoph Anton Mitterer wrote: > On Sun, 2020-10-04 at 14:02 +1100, Damien Miller wrote: > > This is strictly no worse than continuing to use the old key, so I > > don't consider it a problem. > > Well but in reality it will lead to people never again replace their > key by proper means. Well, first I disagree that this method is improper. The

Trying to get SSH agent forwarding working for a popular open source configuration management system called Ansible. I?ve had some unexpected behaviour, the only cause of which I can find is how I express the command line arguments. http://stackoverflow.com/questions/20952689/vagrant-ssh-agent-forwarding-how-is-it-working?noredirect=1#comment31511341_20952689 In summarise: In the first

https://bugzilla.mindrot.org/show_bug.cgi?id=2525 Bug ID: 2525 Summary: Please add an alias such as -o Insecure for -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no Product: Portable OpenSSH Version: 6.7p1 Hardware: amd64 OS: Linux Status: NEW Severity:

https://bugzilla.mindrot.org/show_bug.cgi?id=1993 alex at testcore.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alex at testcore.net Version|5.9p1 |6.2p1 --- Comment #1 from alex at testcore.net --- Also

As far as I can tell, there currently isn't a straightforward way to use password authentication for connecting to hosts where the host key changes frequently. I realize this is a fairly niche use case, but when developing software for devices that often get reimaged (resulting in a host key change), it can get pretty tedious to attempt to connect, get a warning, remove the old host key via

Hello all. I wrote this small patch that allows having multiple tags on a configuration block in the openssh client configuration. For instance, with this configuration: > Host test-host > Tag change-hostname change-port-and-user > Tag jump-to-mybox > > Match tagged change-hostname > Hostname new-hostname > > Match tagged change-port-and-user > Port 12345 >

Greetings CentOS community! I connect to a very large number of new machines with a handful of my CentOS boxen. Whenever I connect to a new host, I *REALLY* would like to *NOT* see the error message such as this: The authenticity of host 'w.x.y.z (w.x.y.z)' can't be established. RSA key fingerprint is 62:7a:6c:e5:03:f5:47:be:23:a5:c5:e5:c3:60:9b:8d. Are you sure you want to continue