It has been fixed upstream:
http://www.openssh.com/txt/release-6.9
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/510732
Title:
OpenSSH server sshd_config PermitRootLogin - NO
To
This one can probably be closed since the default is now
PermitRootLogin without-password and that's close enough.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/510732
Title:
Public bug reported:
According to the manual page, scp should be able to copy between two
remote hosts:
scp user@host1:file1 user@host2:.
However, it fails after asking for the password for the first host, even
though the same file can be copied in two steps:
$ scp xx.yy.zz.aa:*.csv
Public bug reported:
The 4 and5 Apr i386 images won't install openssh-server due to unmet
dependencies.
http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/66090/downloads
$ sudo apt-get install openssh-server
Reading package lists... Done
Building dependency tree
Reading state
trumpetti.atm.tut.fi AKA fi.archive.ubuntu.com is out of sync
** Changed in: openssh (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1303265
It seems fixed in trusty. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to screen in Ubuntu.
https://bugs.launchpad.net/bugs/1173312
Title:
screen : chmod /dev/pts/6: Operation not permitted
To manage notifications about
I can do the Server system, too, but right now the steps I have followed
to get the problem are:
1. install Ubuntu 12.04 desktop, or Lubuntu 14.04devel desktop (it occurs on
both)
2. install Apache2, leaving default configuration settings
3. load an html page from the server in a browser (in
The one browser is Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0)
Gecko/20100101 Firefox/25.0
HTTP_ACCEPT Headers :
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 gzip, deflate
en,en-us;q=0.7,sv;q=0.3
The other is: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:25.0)
I've done a fresh installation from the ubuntu-12.04.3-server-i386.iso
image and installed Apache2. The Firefox web browser still shows that
the pages being served are encoded in windows-1252 instead of UTF-8,
which is what the locale is set to, or ISO-8859 which would be the old
standard.
--
If I serve a UTF-8 encoded file *AND* set the default myself in Apache,
then everything is fine. If the default encoding is left alone, Apache
serves it up as windows-1252 and then UTF-8 encoded letters come out
as garbage like this: åäöÅÄÖéÉ
As seen from the browser HTTP_ACCEPT Headers,
If wget is not seeing the wrong encoding then it may be a problem with
Firefox instead.
However, the steps to reproduce are
1. install Ubuntu 12.04 desktop, or Lubuntu 14.04devel desktop (it occurs on
both)
2. install Apache2, leaving default configuration settings
3. load an html page from the
It looks like the problem is Firefox then. If no default is set, then
it sends wget 'Content-Type: text/html'. If the default is set to
utf-8, then it sends wget 'Content-Type: text/html; charset=utf-8'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Public bug reported:
Apache2 by mistake defaults to windows-1252 instead of UTF-8. The
system is now in UTF-8 or at worst ISO-8859. Apache2 should default to
a standard character set, such as UTF-8 which is used in the rest of the
system.
$ set | grep -i utf
LANG=en_US.UTF-8
ProblemType: Bug
No change. It's still there in 13.10 and this version of fancontrol:
$ apt-cache policy fancontrol
fancontrol:
Installed: 1:3.3.3-1ubuntu1
Candidate: 1:3.3.3-1ubuntu1
Version table:
*** 1:3.3.3-1ubuntu1 0
500 http://fi.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
Public bug reported:
The editor Kompozer has been provided by earlier releases of Ubuntu.
Please package it for Saucy and Raring.
http://www.kompozer.net/download.php
** Affects: kompozer (Ubuntu)
Importance: Undecided
Status: New
** Tags: needs-packaging
** Package changed:
Public bug reported:
ssh-add seems not to work with the confirmation (-c) option. Trying to
require that identities be subject to confirmation when used brings up
the error Error reading response length from authentication socket.
$ ssh-add -c /home/user/.ssh/key_rsa
Enter passphrase for
It then gives the error Agent admitted failure to sign using the key.
$ eval `ssh-agent`
Agent pid 9903
$ ssh-add -c /home/user/.ssh/key_rsa
Enter passphrase for /home/user/.ssh/key_5501_rsa:
Identity added: /home/user/.ssh/key_rsa (/home/user/.ssh/key_rsa)
The user must confirm each use of
This is with a plain vanilla Quantal (Lubuntu) installation installed
just today and have not changed the configurations on. So the settings
used are default. SSH_ASKPASS is not getting set:
$ echo $SSH_ASKPASS
$ echo $DISPLAY
:0
--
You received this bug notification because you are a member
** Package changed: openssh (Ubuntu) = gnome-keyring (Ubuntu)
** Changed in: gnome-keyring (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
Public bug reported:
Now that sshd is an upstart service, the file /etc/default/ssh is not
needed and should be removed to avoid confusion. The settings are now
made at the end of /etc/init/ssh.conf instead.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: openssh-server 1:6.0p1-3ubuntu1
Can there be a config file included in the default install that contains
such a message? A pointer is needed to the solution somehow.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
Could a post-install script ask to run pwmconfig and then run it if the
answer is yes?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/884177
Title:
fancontrol should have
Public bug reported:
If upstart is indeed where Ubuntu is heading then ntp ought to be
migrated over to it before 12.04.
Below is a guess at what /etc/init/ntp.conf could contain. Some other
changes are needed for it to work properly.
# ntp - Network Time Protoco client and server
#
# The
Public bug reported:
If Upstart is indeed the way Ubuntu is moving then Apache2 should
migrate from SystemV scripts to Upstart in time for the next LTS in
12.04. A configuration file is needed in /etc/init plus a few other
changes.
** Affects: apache2 (Ubuntu)
Importance: Undecided
The problem is also present in Precise.
$ lsb_release -rd
Description:Ubuntu precise (development branch)
Release:12.04
$ fancontrol
Loading configuration from /etc/fancontrol ...
Error: Can't read configuration file
$ apt-cache policy fancontrol
fancontrol:
Installed:
Still present in Precise:
$ lsb_release -rd
Description:Ubuntu precise (development branch)
Release:12.04
$ apt-cache policy fancontrol
fancontrol:
Installed: (none)
Candidate: 1:3.3.0-4ubuntu1
Version table:
1:3.3.0-4ubuntu1 0
500
Public bug reported:
$ fancontrol
Loading configuration from /etc/fancontrol ...
Error: Can't read configuration file
$ lsb_release -rd
Description:Ubuntu 11.10
Release:11.10
~$ apt-cache policy fancontrol
fancontrol:
Installed: 1:3.3.0-4ubuntu1
Candidate: 1:3.3.0-4ubuntu1
Public bug reported:
The value for Tm0P is bogus. If it is not a real sensor, then it should
not be listed. If it is a real sensor, then it should show the real
temperature, not a bogus value.
$ sensors
nouveau-pci-0200
Adapter: PCI adapter
temp1:+73.0°C (high = +100.0°C, crit =
** Attachment added: dmesg
https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/884173/+attachment/2580036/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
It appears that the configuration file is missing.
$ ls /etc/fancontrol
ls: cannot access /etc/fancontrol: No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
$ dpkg -L fancontrol
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/fancontrol
/usr/share/doc/fancontrol/copyright
/usr/share/doc/fancontrol/fancontrol.txt.gz
/usr/share/doc/fancontrol/changelog.Debian.gz
/usr/share/man
/usr/share/man/man8
/usr/share/man/man8/fancontrol.8.gz
It's a work around but I'd still expect dig to return a non-zero number
sometimes.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/854705
Title:
dig returns 0 regardless of result of
Public bug reported:
/usr/bin/dig returns 0 regardless of whether the query was successful or
not. It should return 0 instead if the query failed.
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Sorry it should return 1 instead if the query failed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/854705
Title:
dig returns 0 regardless of result of query
To manage
I would expect dig to respond in this manner:
dig +short www.google.com echo SUCCESS || echo FAILURE
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/854705
Title:
dig returns 0
Public bug reported:
Binary package hint: ntp
NTPd has four time severs in the ubuntu server pool. It might be good
to add a few extra lines to the bottom of the servers list to provide
your current local time as a default should the machine temporarly lose
Internet connectivity:
server
Don't argue about it. Just make the correction by setting it to No
--
OpenSSH server sshd_config PermitRootLogin - NO
https://bugs.launchpad.net/bugs/510732
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Jamie, the various backup strategies that I have seen are all suited to
using sudo. They all run a program or script which receives some
arguments at run time. That includes rsync over ssh. Could you please
be specific about which backup strategy is not able to work with sudo?
Kees, yes, I see
The default Ubuntu Server install does *not* have openssh-server
installed.
Ok, then that's a separate bug needing a separate bug report.
Nearly all installations of the openssh-server package, I am guessing
then, are on the Ubuntu Server or an alternate install tuned to be
rather like the
Public bug reported:
Ubuntu does not use the root account directly so the PermitRootLogin
directive in sshd_config should be set to no by default. This policy
is backed by the upstream documentation:
For security reasons, it is bad practice to log in as root during regular
use and
Hmm. Wishlist is not the right category for a bug.
Mathias, defaulting PermitRootLogin to no improves the layered process
of 'security' for the default installation by adding another layer of
protection and not relying on the hope that the root account will always
remain disabled. Correcting
Thank you for the cheezburger link, Kees. From it, I am starting to
understand more about how decisions are made in the Ubuntu project and
the authoritative resources drawn upon to help make informed decisions.
Anyhow, those that somehow get the impression that they want to log in
as root can
Chuck, what information do you think is missing?
--
/etc/init.d/apache2 missing option to stop gracefully
https://bugs.launchpad.net/bugs/456381
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Ubuntu-server-bugs
$ apt-cache policy apache2
apache2:
Installed: 2.2.12-1ubuntu2
Candidate: 2.2.12-1ubuntu2
Version table:
*** 2.2.12-1ubuntu2 0
500 http://fi.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
$ lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
@Colin:
Ok. I see enough guessing in the postings here, including mine, that
expert advice is needed. Where can we find an authoritative statement
from People Who Have Better Real Cryptographer Credentials as to a 'best
practice' for key type and key size? The manpage at least should
provide a
Public bug reported:
Binary package hint: openssh-client
Currently ssh-keygen generates RSA keys by default. It's probably time
for these to be depreciated in favor of DSA keys.
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
ssh-keygen should default to dsa
@Neal: That's a valid critique of debian's SSL implementation not
related to DSA vs RSA.
DSA is faster for signing and RSA is faster for verification.
http://neubia.com/archives/000191.html
ftp://ftp.rfc-editor.org/in-notes/rfc2536.txt
http://home.pacbell.net/tpanero/crypto/dsa.html
RSA
47 matches
Mail list logo
