similar to: Disabling AAAA DNS record lookups?

My head hurts from trying to figure this out for the past several hours . . . I want to determine what provider to use based on a fact (thanks for the suse version fact btw) but I ain''t gettin it: What''s wrong? Am I going down the completely wrong path? Is there a better way? # suse-yum.pp case $suse_repo_name { #sled10-i586: {Package{ provider => rug}} sled10-i586:

I have Asterisk running on a Ubuntu 18.0.4 on Digital Ocean. Every so often asterisk crashes and then restarts. I am not seeing any core dumps on the box. The only I thing I see every time is a second before Asterisk crashes there is a AAAA lookup for the boxes hostname. As soon as it gets the response I see that asterisk is restarting. Any idea what would cause this and how would get a dump or

On Tue, Jun 26, 2018 at 7:59 PM, Richard Mudgett <rmudgett at digium.com> wrote: > > > On Tue, Jun 26, 2018 at 6:15 PM, Dovid Bender <dovid at telecurve.com> wrote: > >> I have Asterisk running on a Ubuntu 18.0.4 on Digital Ocean. Every so >> often asterisk crashes and then restarts. I am not seeing any core dumps on >> the box. The only I thing I see

https://bugzilla.mindrot.org/show_bug.cgi?id=2391 Bug ID: 2391 Summary: Enhance AllowGroups documentation in man page Product: Portable OpenSSH Version: 6.8p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: Documentation Assignee:

Hi, I'm installing a few linux clients and one server with samba. The network addresses are IPv6 in the .local domain. The avahi-daemon implements de MDSN resolver. A standard "ping6 -Ieth0 servername.local" generates a "AAAA" query packet which is correctly responded by the servername.local machine and the ping works fine. "smbclient -L servername.local"

I've the following error : Doing a node status request to the domain master browser at IP aaaa.bbbb.cccc.dddd failed First time I configure my smb.conf file on a server with the adress aaaa.bbbb.cccc.dddd For some raison I have to change this address for another. When I restart samba I the message : nmbd/nmbd_browsesync.c:get_domain_master_name_node_status_fail(486)

Hi, I'm experimenting with setting up winbind and so forth on a simple system joined to an existing AD domain and I've seem to run into some rather broken behavior with DNS updates. As everyone knows, Active Directory is heavily dependent on DNS and it's good to make sure that the DNS records for each system joined to the domain stay up-to-date. So I'm testing to make sure that

Hello all, I am trying to find out how the AAAA records are added in my SambA AD DC setup but it is not clear how they should be added. Here are my zones: ? pszZoneName???????????????? : 56.168.192.in-addr.arpa ? Flags?????????????????????? : DNS_RPC_ZONE_DSINTEGRATED DNS_RPC_ZONE_UPDATE_SECURE ? ZoneType??????????????????? : DNS_ZONE_TYPE_PRIMARY ? Version???????????????????? : 50 ?

I am trying to setup dynamic updates with bind_dlz backend, but for some reason if any windows client or linux with nsupdate tries to remove AAAA record, server just 'cancelling transaction', while A and PTR records (both on reverse ipv4 and ipv6) working fine. If i'am remove AAAA record manually via samba-tool or windows mmc then AAAA record can be updated, but after that it again

Hi, After extensively looking into puppet + augeas for managing the AllowGroups in sshd_config, I came to the conclusion that it won''t work as I expected :( So I''m sharing my thoughts here. The main objective is allowing multiple groups per-node, depending on what the security team wants. Since I want this to be dynamic, I created a define in a class: class ssh::server::config

Hai, I have AllowGroups sshlinux, sshwindows Add at least 1 user in the linux group and at least 1 in the sshwindows group. Make sure the sshwindows group have a GID. And make sure the windows user loggin in in ssh als have a UID. AND for both, UID 1000+ ( which is in debian the default PAM setting ) . This is base on a "MEMBER" server. If you do : getent windowsuser You

Markus, ignore the other stuff I sent.. I need to go back to bed and stop trying to code.. <sigh> For everone else.. Will this make everyone happy? This does the follow. it will always honor AllowUsers. If there is no Allow/DenyGroups it stated they are not in allowUsers. IF there are AllowDenyGroups it tries them. And then stated they are not in either AllowUsers nor AllowGroups

Hey, After discussing the limit of MAX_ALLOW_USERS I've been trying to use AllowGroups instead. In the config file I have the AllowUsers lines before the AllowGroups lines (I have tried both ways) and it appears that the presence on the AllowGroups directives seems to blow away any Allow* directives I have set. I'm not sure how to check further for bugs so I figured I'd contact

What I was trying to do: I wanted to use the AllowGroups facility to allow users in by group instead of listing individual usernames but also allow root only from a single central host. Setup actions: targetusername on target host has a secondary group entry of "staff". Updated sshd_config to add the lines: AllowUsers root at nimsrvr AllowGroups staff targertusername is NOT

Hi, with sssd i can do: $ ssh user at domain.tld@HOST1 $ id user at domain.tld $ ls -al /home/domain.tld/user drwx------ 5 user at domain.tld domain users at domain.tld 103 12. Jun 14:14 . $ grep AllowGroups /etc/ssh/sshd_config AllowGroups lokale_gruppe samba_gruppe at domain.tld When switching to winbind only $ id user at domain.tld is working any other command is using user\domain $ ls -al

While testing some AllowUsers and AllowGroups combinations I was surprised to find that one cannot be used to override the other. For example: AllowGroups administrators AllowUsers john If john is *not* part of the administrators group, then access is being denied. Is this the expected behaviour? This would force me to create another group just for ssh, something like ssh-admins. This other

Hi! I'm experimenting with migrating the custom sshd_config settings for our (Debian bullseye, openssh-server 8.4) server environment into fragments under sshd_config.d/, and am wondering about sshd's behaviour when encountering multiple AllowGroup lines. The manual states "For each keyword, the first obtained value will be used.", so that gives me the impression that any

Hey everyone, After discussing the AllowGroups I think I've discovered a bug. The system is a solaris 8 system and the problem is that when I use AllowGroups with no AllowUsers args, the proper actions happen. Same with AllowUsers and no AllowGroups. When I try to combine the two, none of the Allow directives seem to take. Is it just me or maybe a bug? -James

Subject: logcheck-database: Tweak to ssh rules to ignore AllowGroups denial Package: logcheck-database Version: 1.3.13 Severity: minor *** Please type your report below this line *** Similar to how AllowUsers denials are ignored, also ignore AllowGroups: ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ sshd\[[[:digit:]]+\]: User [-_.[:alnum:]]+ from [-_.[:alnum:]]+ not allowed because none of

I smacked into this previously reported bug today whereby an invalid keyword in the Match{} stanza did not throw an error on configuration reload. Are there any plans to fix this? Likewise the penchant for some fields to be comma separated and others to be spaces is just asking for mistakes. Why not support both and be done with it? There was no response (that I saw in the archives) to this post