search for: l297

...s, work "everywhere": https://doc.dovecot.org/configuration_manual/config_file/config_variables/#variables-global However, the source code for driver-pgsql.c indicates that the connect string is never expanded: https://github.com/dovecot/core/blob/master/src/lib-sql/driver-pgsql.c#L297 For reference, this is my configuration. dovecot.conf: import_environment = PASSDB_USER PASSDB_DBNAME PASSDB_PASSWORD passdb { override_fields = proxy=y driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } /etc/dovecot/dovecot-sql.conf.ext: driver = pgsql connec...

Hi, It seems that some versions of ssh-agent get confused by ECDSA-SK keys. >From my OpenBSD-current laptop, I'm trying to do remote system adminstration on a machine running Debian 8 with the stock ssh package (OpenSSH_6.7p1 Debian-5+deb8u8, OpenSSL 1.0.2l 25 May 2017). I need access to a remote gitlab server to fetch files with git, using an ED25519 key in my ssh-agent. Once connected

...8-cbc Digest = sha512 I am a bit surprised that the router's tinc manages to talk to Debian's tinc, when I set a cipher suite that the router's SSL library does not recognise. I looked at the log, it triggers this line: https://github.com/gsliepen/tinc/blob/master/src/protocol_auth.c#L297 I am just wondering, what happens after metakey_h() returns false? Does tinc simply fall bacck to a more common cipher? Do the two clients neogiate what to fallback to? FF

...since it does not actually read the variables: it just lists the writable ones, and allows one to set them. But the OpenUPS driver does not list any HID usage items as read/write, or as commands, so that is to be expected: https://github.com/networkupstools/nut/blob/master/drivers/openups-hid.c#L297 NUT takes a somewhat conservative approach to the USB HID drivers: we only query for variables and commands that are known to work with that vendor's UPS. There are some debug modes available in usbhid-ups that would list all of the potential variables that the firmware supports, but you may n...

>That address seems to come from >here: https://github.com/torvalds/linux/blob/5924bbecd0267d87c24110cbe2041b5075173a25/arch/x86/boot/pm.c#L124 > >``` >protected_mode_jump(boot_params.hdr.code32_start, > (u32)&boot_params + (ds() << 4)); >``` > >That boot_params.hdr.code32_start field is probably either invalid (bad reloc or something else causing the

I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6. I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow! I?ve got