[Bug 1510318] [NEW] Augeas 1.3 can't read some conf files
Public bug reported: https://github.com/hercules-team/augeas/issues/191 Augaes 1.3 can't read certain ssl.conf files, such as one of the ones Let's Encrypt uses: https://github.com/letsencrypt/letsencrypt/issues/981 versions 1.2 and 1.4 of augaes don't have this problem, but currently vivid and wily are distributing version 1.3: http://packages.ubuntu.com/search?keywords=augeas-lenses For Let's Encrypt to work for all Ubuntu users this bug should be fixed for them. ** Affects: augeas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to augeas in Ubuntu. https://bugs.launchpad.net/bugs/1510318 Title: Augeas 1.3 can't read some conf files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1510318/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
I agree with Eric and cloudcontrol, for CNAMEs being the correct solution. In the meantime, there's a problem with using any debian package from within ec2 instances - you can't contact the repository to install any packages, so using a package to fix the problem presents something of a bootstrapping problem. That includes, by the way, anything that requires apt-mirror, since apt- mirror is not part of the barebones Lucid AMI, and thus requires installation, which requires connecting to the repo... I have an alternative solution, which requires no package installation, and which I will be using until this problem is fixed. Rather than installing packages, I have chosen the simpler direct manipulation of the sources.list file, like this: sed -i -e 's/eu-west-1.ec2/uk/' /etc/apt/sources.list Change 'uk' to be whatever your closest mirror is, and you'll be running again. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 309160] Re: openssh public key auth broken if one has many keys but only in X11
workaround/fix: - move all keys into subdirectories and update config to reflect changes. - even with multiple keys in subdirectories it does not try the wrong keys. hypothesis: - the ssh client looks in ~/.ssh and tries any files it deems to be keys, even when 'config' is configured explicitly with the appropriate key. Fortunately, it does not recurse into subdirs.n other observations: - the behaviour persists without a config file and specifying the key on the command line (ie. ssh -i keyfile host) - this fixes putty, also (must have been patched to use ~/.ssh at some time) -- openssh public key auth broken if one has many keys but only in X11 https://bugs.launchpad.net/bugs/309160 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 309160] Re: openssh public key auth broken if one has many keys but only in X11
putty (0.60-3) fails with the same error (too many authentication errors). putty is not configured at all on this machine so it should be in passwd auth mode. However, ss soon as I put in my login name it comes up with the error. -- openssh public key auth broken if one has many keys but only in X11 https://bugs.launchpad.net/bugs/309160 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 309160] [NEW] openssh public key auth broken if one has many keys but only in X11
Public bug reported: Binary package hint: openssh-client After upgrading from 8.04 to 8.10, I could not log into any machines via ssh where I had already configured public-key auth. This happens with both rsa and dsa keys. The error given was: "Received disconnect from 10.0.0.1: 2: Too many authentication failures for " `ssh -vvv ` showed that ssh client was trying keys randomly(?), even though ~/.ssh/config specified the key properly (and has always worked in the past). workaround 1: If I remove all the keys from ~/.ssh/ except for the host I was trying, I could then log into that host successfully while in X11. workaround 2: use ssh client directly from the console (with or without X11 running on anther vty) $ apt-cache policy openssh-client openssh-client: Installed: 1:5.1p1-3ubuntu1 Script started on Wed 17 Dec 2008 03:24:11 PM EST [nd...@ganymede] [jobs:0] [exit:0] [cpu:44C] [15:24] [12/17/08] [~] $ ssh -vvv io OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /home/ndain/.ssh/config debug1: Applying options for io debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to io.jovian.local [10.0.0.1] port 22. debug1: Connection established. debug3: Not a RSA1 key file /home/ndain/.ssh/id_dsa-nd...@mynetworks.priv. debug2: key_type_from_name: unknown key type '-BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-END' debug3: key_read: missing keytype debug1: identity file /home/ndain/.ssh/id_dsa-nd...@mynetworks.priv type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7p1 Debian-8ubuntu1.2 debug1: match: OpenSSH_4.7p1 Debian-8ubuntu1.2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-3ubuntu1 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-cbc hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug2: dh_gen_key: priv key bits set: 125/256 debug2: bits set: 512/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: check_host_in_hostfile: filename /home/ndain/.ssh/known_hosts debug3: check_host_in_hostfile: match line 21 debug1: Host 'io.jovian.local' is known and matches the RSA host key. debug1: Found key in /home/ndain/.ssh/known_hosts:21 debug2: bits set: 482/1024 debug1: ssh_rsa_verify: si
Re: [Bug 89364] Re: Apache2 default site contains only the words "It works!"
How about forwarding to Apache, where the bug is still WONTFIX. On Fri, Sep 26, 2008 at 11:36:09AM -, Soren Hansen wrote: > On Thu, Sep 25, 2008 at 09:02:00PM -, Loye Young wrote: > > > > > > IT WORKS! > > > > This is the default web page for this server. > > > > The fact that you see this page means that the host computer is booted up, > > the web server software is running, and the networking between your computer > > and the host computer is functioning properly. > > > > If this page is not what you expected, there are many possible causes. Check > > with the owner or administrator of the server for more information. > > > > > > Hm... I kind of like that, actually :) > > Does anyone feel like forwarding this suggestion to Debian? > -- Noah Slater, http://bytesexual.org/nslater -- Apache2 default site contains only the words "It works!" https://bugs.launchpad.net/bugs/89364 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
