We, and a lot of other enterprise sites are using Kerberos, so we would
like it to be on by default.
--
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/84899
Title:
SSH with
I extracted the megatec_usb and blazer_usb from the 2.4.1-3ubuntu2 and
tried them using the method in comment 5. No sucess though.
** Attachment added: Test with the Blazer driver from karmic (2.4.1-3ubuntu2)
http://launchpadlibrarian.net/34425912/blazer-karmic.txt
--
megatec_usb does not
** Attachment added: Test with the megatec_usb driver from karmic
(2.4.1-3ubuntu2)
http://launchpadlibrarian.net/34425930/megatec-karmic.txt
--
megatec_usb does not work anymore with a Trust PW-4130M UPS
https://bugs.launchpad.net/bugs/447586
You received this bug notification because you
megatec_usb from trunk still fails.
blazer_usb from trunk does work, but not blazer_usb from 2.4.1-2ubuntu4.
** Attachment added: megatec_usb from trunk
http://launchpadlibrarian.net/33423172/megatec_usb-trunk.txt
--
megatec_usb does not work anymore with a Trust PW-4130M UPS
** Attachment added: blazer_usb from 2.4.1-2ubuntu4
http://launchpadlibrarian.net/33423193/blazer-2.4.1.txt
--
megatec_usb does not work anymore with a Trust PW-4130M UPS
https://bugs.launchpad.net/bugs/447586
You received this bug notification because you are a member of Ubuntu
Server Team,
** Attachment added: blazer_usb from trunk
http://launchpadlibrarian.net/33423200/blazer.txt
--
megatec_usb does not work anymore with a Trust PW-4130M UPS
https://bugs.launchpad.net/bugs/447586
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Binary package hint: nut
I have recently upgraded from hardy to intrepid to jaunty. After
upgrading to Intrepid the megatec_usb stopped recognizing my Trust PW-
4130M ups, it still does not work on Jaunty. It worked without any
problems in hardy.
I tried the megatec_usb
** Attachment added: Output from running the driver in jaunty
http://launchpadlibrarian.net/33376912/megatec_usb-2.4.1.txt
--
megatec_usb does not work anymore with a Trust PW-4130M UPS
https://bugs.launchpad.net/bugs/447586
You received this bug notification because you are a member of
** Attachment added: Output from lsusb
http://launchpadlibrarian.net/33377040/trust-lsusb.txt
--
megatec_usb does not work anymore with a Trust PW-4130M UPS
https://bugs.launchpad.net/bugs/447586
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Attachment added: Output from the hardy driver
http://launchpadlibrarian.net/33377007/megatec_usb-2.2.1.txt
--
megatec_usb does not work anymore with a Trust PW-4130M UPS
https://bugs.launchpad.net/bugs/447586
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
Please upgrade the patch set from Simon Wilkinson for support of
Cascading Credentials (and also updates to GSSAPI key exchange)
See: http://www.sxw.org.uk/computing/patches/openssh.html
ProblemType: Bug
Architecture: amd64
Date: Fri Aug 21 15:47:12 2009
DistroRelease:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30640742/Dependencies.txt
--
GSSAPI Cascading Credentials support
https://bugs.launchpad.net/bugs/416958
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in
I'm not so sure that dropping it to a suggestion is a good idea. A lot
server software are managed by a GUI, which you need to run remote.
--
openssh-client could suggest xauth rather than recommend it
https://bugs.launchpad.net/bugs/270512
You received this bug notification because you are a
Of course. Why should I keep them if I don't use them.
--
ssh's init script should generate host keys if they're missing
https://bugs.launchpad.net/bugs/246558
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Well. It complains that it can't find any hostkeys when started (and
when logging in) but it works perfectly well without hostkeys when using
GSSAPI. As we are only allowing GSSAPI on most of our machines there is
really no need for the hostkey as the host authenticity is established
using the
Host keys are not necessarily needed when running openssh-server, i.e
when using GSSAPI/Kerberos, and it could actually be argued that it is a
bug if they were generated automatically if not found.
Please make it configurable if you want the keys to be generated and
which keys you want to be
If you run scp with the '-v' (verbose) you can see what command is
actually run. It should be in the first line of output.
Without using any \ or (or ') the filename are treated by the local
shell as 3 arguments to scp instead of one; the filename.
In the first case the \ are expanded by the
17 matches
Mail list logo
