search for: authprotocol

...attery.date: 03/14/20 battery.packs: 0.00 battery.packs.bad: -1.00 battery.runtime: 5160.00 battery.runtime.low: 120 battery.voltage: 27.00 battery.voltage.nominal: -1.00 device.mfr: APC device.model: SMART-UPS 1400 device.serial: WS9831004667 device.type: ups driver.name: snmp-ups driver.parameter.authProtocol: MD5 driver.parameter.mibs: apcc driver.parameter.pollinterval: 2 driver.parameter.port: 192.5.37.191 driver.parameter.privProtocol: DES driver.parameter.secLevel: authPriv driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: apcc MIB 1.2 driver.version.internal: 0.97 input.f...

...mission server, and need to set up the dovecot authentication in exim. I'm having an issue with that (documented at <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756258>) The problem is that exim doesn't follow the handshake as described here: <http://wiki2.dovecot.org/Design/AuthProtocol>. The wiki page says that the client should start the handshake, but exim waits for the server to start and to receive the DONE command until it starts its own handshake. What I actually get is: exim connects to dovecot auth dovecot VERSION 1 1 dovecot SPID 48 And...

....g. an SNMP v1 or v2c string) does that user > / community string have read/write access? I tried setting them all with -x thing= arguments as well as letting it pull from ups.conf, same result. It's all SNMPv3 settings. sudo snmp-ups -DDDD -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k The output with -DDDD is the same either way. > tcpdump to listen for packets across UDP 161 is one way to check what is > actually being sent. I guess that really is...

...is, does nut's SNMPv3 implementation work? I have this in /etc/ups/ups.conf ...... [tfapc01] driver = snmp-ups port = tfapc01.testfest.ixorg.org mibs = apcc snmp_version = v3 secLevel = authPriv secName = tfsnmpprof1 authPassword = ralow6moHet7zoboP8 privPassword = tuseL8Pakaz9degim7 authProtocol=MD5 privProtocol=AES desc = "APC SU700 SNMP v3 device, with the highest security level" ...... Now I test /sbin/snmp-ups -DDD -a tfapc01 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '3' 0.000600 SNMP UPS driver : entering upsdrv_initups...

...Scan at Password43LongerWord Authentication protocol: MD5 (only option other than none) Privacy Protocol: DES (only option other than none) In access control I've enabled user nut. However, when I try to use nut-scanner on it: $ nut-scanner -S -s apcups --secLevel authPriv --secName nut --authProtocol MD5 --authPassword NutScan at Password43LongerWord --privProtocol DES --privPassword NutScan at Password43LongerWord Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase snmpwalk gives a different error: $ snmpwalk -v 3 -u nut apcups -x DES -X NutScan at Pa...

...he binaries from EPEL I downloaded the source and compiled for myself with the exact same result. nomad -------------- next part -------------- Script started on 2020-05-04 09:19:50-07:00 ]0;lvd at chscc-pc-052:~: || lvd at chscc-pc-052 ~ [936] ; nut-scanner -S --secLevel authPriv --secName nut --authProtocol MD5 --privProtocol DES --authPassword NutScan at P Password43LongerWord --privPassword NutScan at Password43LongerWord -s apcups Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase ]0;lvd at chscc-pc-052:~: || lvd at chscc-pc-052 ~ [937] ; please snmp-ups -...

...me<https://urldefense.proofpoint.com/v2/url?u=http-3A__driver.name&d=DwMFaQ&c=f9s1WCuF-N6cmD_YaZ7gBg&r=lhr3k4au5dVQgHY_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=VdKSS_Vk98WT0ADZ-mQe_3zCfrLacAAuMS7JSj5wn1w&s=hM67G_Mcn7oW5yo4o44Na9wyw26mxM8hKXFExeGyhJQ&e=>: snmp-ups driver.parameter.authProtocol: MD5 driver.parameter.mibs: apcc driver.parameter.pollinterval: 2 driver.parameter.port: 192.5.37.191 driver.parameter.privProtocol: DES driver.parameter.secLevel: authPriv driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: apcc MIB 1.2 driver.version.internal: 0.97 input.f...

...(ignoring #, of course). [ups1] desc = "APC Smart-UPS 5000 SNMP in rack 1 - AP9617" driver = snmp-ups mibs = apcc port = [ups1...] # snmp_version = v1 # community = [xxx] snmp_version = v3 secLevel = authPriv secName = [xxx] authPassword = [xxx] authProtocol = MD5 privPassword = [xxx] privProtocol = DES [ups2] desc = "APC Smart-UPS 5000 SNMP in rack 2 - AP9619" driver = snmp-ups mibs = apcc port = [ups2...] snmp_version = v1 community = [xxx] # snmp_version = v3 # secLevel = authPriv # secName = [xxx]...

...ps. Heres the config; [ups6]                 Driver = snmp-ups                 Port: ups6.domain.name (also tried 192.168.24.9)                 Snmp_version = v3                 secLevel = authPriv                 secName = ups6                 authPassword = PASSWORDSTRING                 authProtocol = MD5                 privPassword = PASSWORDSTRING                 privProtocol = AES                 pollfreq = 15                 desc = “apc ups” But when I run the service, I get this error # /usr/sbin/upsdrvctl start Network UPS Tools – UPS driver controller 2.7.2 Network UPS...

On 06/06/2017 03:18 PM, Steffen Kaiser wrote: > (!(service=%s)) > > or better name this attribute > > deniedService Thanks, this is quite helpful already. Regarding the other question about all the services that can be used there, I tried to grep the source code for certain keywords but could not really find anything useful with "service", "services" and some

Hi, this is partly Postfix related, but I want to know if there could be way to distinguish port of the SASL AUTH request to segregate user services. Currently I use unix listener for dovecot sasl auth, but could change to inet_listener. Only way I can think is to have different SASL AUTH services for each master.cf entry where its needed. But is it possible for Dovecot to have more than

Hi all, I'm reading dovecot source codes(2.0.13),and I need to know how dovecot communicate with sasl? I traced the source code from cmd_login function,and found out something about sasl_callback. but i never found where this function called and also I couldn't understand how sasl inform the dovecot from authentication result. I'll be thankful if someone could help me out.

Hi After upgrading the kernel, everything is fine, except dovecot authentication. I get this trange thing (data after REQUEST? changed just in case it contains anything sensitive): Nov 29 16:56:01 volanges dovecot: auth: Error: BUG: Authentication client sent unknown handshake command: REQUEST?6970356762?616?6?235264ef69dbd1665538af54d12fdaea?session_pid=453?req... Nov 29 16:56:01 volanges

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm using Dovecot v2.2 with unix_listener auth-client { } to verify passwords for a different service. However, it looks like that auth_failure_delay effects all connects going through that socket. I mean: connect /var/run/dovecot2.2/auth-client attempt bad auth 2s penalty NO disconnect ==> Note, it's another connection almost

...Scan at Password43LongerWord Authentication protocol: MD5 (only option other than none) Privacy Protocol: DES (only option other than none) In access control I've enabled user nut. However, when I try to use nut-scanner on it: $ nut-scanner -S -s apcups --secLevel authPriv --secName nut --authProtocol MD5 --authPassword NutScan at Password43LongerWord --privProtocol DES --privPassword NutScan at Password43LongerWord Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase snmpwalk gives a different error: $ snmpwalk -v 3 -u nut apcups -x DES -X NutScan at Pa...

...ot a config problem. I've just tried the same command from a FBSD box with the same unfortunate result. Mind you, it could be the UPS card, I'm using the same one for both tests. : || nomad at castle nut-2.7.4 [93] ; please drivers/snmp-ups -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k Network UPS Tools - Generic SNMP UPS driver 0.97 (2.7.4) No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.10'! Please report it to NUT developers, with an '...

Hi, Every time that I have to restart the nut-server it's a nightmare. For example, after editing ups.conf In many cases the only "solution" is to reboot the system. These are the errors: systemctl -l status nut-driver ? nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static; vendor preset:

...es to doc/wiki/ in the tarball and changing: - http://wiki.dovecot.org/* links to doc/wiki/*.txt in dovecot-example.conf - doc/variables.txt could be removed and links to it updated to doc/wiki/Variables.txt - doc/auth-protocol.txt is also already in wiki. Maybe create doc/design/ and put the AuthProtocol.txt there and other design wiki pages there as well. As for v1.0, it looks like there aren't many bug reports anymore about rc27. If there are as few for rc28, I'll release v1.0 in about a month. So unless something special happens, I'll fix only the simplest bugs after rc28 and leave...

...= hostname snmp_version = v3 secLevel = authPriv # 4 lowercase ascii letters secName = xxxx # # 16 lower case ascii letters authPassword = xxxxxxxxxxxxxxxx # 15 lower case ascii letters privPassword = yyyyyyyyyyyyyyy authProtocol = SHA privProtocol = AES [..] * driver debug output and tcpdump attached in nuttrace & nut.pcap Searching for 9630 i found some similar reports to mailing list nut-upsuser from 2013, 2014 and 2016 indicating that others have this problem too. The oldest report suggests to use DES in...