WTF happened to ssh?
by Tom Horsley
I have a ssh tunnel setup between work and home, port 8022 on
my home system is forwarded to port 22 on my work system, so
I can ssh into work on port 8022.
After some recent update, I can no longer ssh into work
from home when I am running as my normal user at home. I get
permission denied.
When I su -l to root at home and try to ssh into work, it works fine.
What the heck is up with that? Who changed what that
could have that effect?
I get the same password prompt. I type the same password.
I'm lost here.
(fully updated fedora 19 64bit at home and at work).
10 years, 4 months
Better way to upgrade fc8->fc19
by Bill Davidsen
I have has miserable luck with fedup, is there a better way, anything? I really
don't want to leave this machine down for days, and the 18->19 on a test machine
took about 36 hours to complete, and another 3-4 to redo all the scripts from
the ones on other machines which all use ethN to meaningless interface names. In
18 I just changed a single script to use (or not use) biosnames, and all was
well, but on my test conversion to 19 that doesn't work, or the file was
rewritten, and I finally used the name which changes every time the machine gets
shuffled a bit.
Is there a better way?
--
Bill Davidsen <davidsen(a)tmr.com>
"'Nothing to hide' does not imply 'nothing to fear'"
- me
"AT&T could not seriously contend that a reasonable entity in its position
could have believed that the alleged domestic dragnet was legal."
-judge Vaughn R. Walker of the U.S. District Court
for the Northern District of California, EFF vs. AT&T
10 years, 4 months
screen-lock doesn't appear to work properly F18, F19 KDE
by DB
Good evening all - at least, it is evening here in Austria!
My 2nd machine is a Toshiba Equium A60-692, with a (massive!) 40GB
harddrive & a (minute!) 750MB RAM.
It used to work fine, then I tried to fedup from F17 to F18......
Most of the time it would work fine, as long as I kept the mouse moving.
If I let the mouse stand still for too long, the screen would go black
& a couple of seconds later the cursor would vanish & I'd have to do a
power down restart to get the system back. Same story if I did a
right-click & lock screen - no wa to get the screen back.
Tried a fresh install of F18, same result; fresh install of F19 same
result (all with KDE)
Tried a fresh install of XFCE F19 Live, everything works fine.
Does anyone have any idea what might be stopping screen-lock from
working? Or how to go about finding out what is really happening???
As ever, many thanks for any ideas!!
Dave
10 years, 4 months
Re: Writing English.
by Zach Ploskey
On Fri, Nov 22, 2013 at 1:44 PM, Chris Murphy <lists(a)colorremedies.com>wrote:
> Nope, you're wrong. Find a copy of New Oxford American Dictionary and look
> up the words and usage. I seriously doubt even Oxford English makes such a
> big distinction between two words that share the same etymology and have no
> good reason for meaning different things.
You beat me to this. Here is the OED definition:
http://www.oed.com/view/Entry/5796?rskey=rEVqSp&result=1&isAdvanced=false...
The adjective forms of alternate and alternative are synonymous in both
British and American English. The current usage of alternate is correct.
Zach Ploskey
10 years, 4 months
xfce, gnome and kde
by Rafnews
Hi,
i installed on a very old laptop Fedora 19. Firstly i must say that
fedora is my favorite OS especially for very old hardware as it works
everywhere.
so this laptop is for my son to watch cartoons and other children things.
when it runs KDE, cartoons are choppy...
when it runs XFCE, cartoons runs like hell...so fast, so well
when it installed Gnome (to test gnome 2 for example), well... it
doesn't allow me to use the gnome shell at all... system display white
screen and i must to log off and to chose another desktop
so how can i do to make KDE or gnome running movies like hell, like
under XFCE desktop ?
thx.
A.
10 years, 4 months
Re: Why some say "rpm hell"
by AP
On Thu, Nov 21, 2013 at 9:06 PM, Heinz Diehl <htd(a)fritha.org> wrote:
> What precisely are you asking for?
Just wanted to know if rpm is better than apt or vice-versa or both
are equal...or why did this bifurcation took place if the Linux is
only the kernel...?
Thanks.
10 years, 4 months
Re: Why some say "rpm hell"
by AP
On Thu, Nov 21, 2013 at 10:21 PM, Greg Woods <woods(a)ucar.edu> wrote:
> Probably a reference to the very early days of RPM (pre-yum). You'd
> install a package, then find some library was missing and go to install
> that, which led to something else missing, etc. A few cycles of this and
> you know what "dependency hell" means. Nowadays, with yum, all the
> dependencies are pulled in automatically, so "rpm hell" is largely a
> thing of the past.
Okay got it. I don't think saying it is worthy nowadays. But for an
end user this all won't matter anytime.
10 years, 5 months
Re: Why some say "rpm hell"
by AP
On Thu, Nov 21, 2013 at 9:08 PM, Dr. Michael J. Chudobiak
<mjc(a)avtechpulse.com> wrote:
> yum didn't always exist. yum handles the dependencies between packages.
Ok.
> Before that, a lot of prayer was involved if you mixed rpm packages from
> different sources.
You mean from third party sources.
10 years, 5 months
openssh-6.3p1-5.fc20 fails with "EC_KEY_new_by_curve_name failed"
by Corinna Vinschen
Hi,
https://admin.fedoraproject.org/updates/FEDORA-2013-19918/openssh-6.3p1-4...
claims openssh-6.3p1-4 and later, in conjuntion with openssl-1.0.1e-30.fc20
will allow to use ECDSA keys for pubkey authentication.
I have existing ECDSA keys from my non-Fedora installations using
vanilla openssh and openssl packages.
So I installed openssh-6.3p1-5 and openssl-1.0.1e-30. When trying to
use the aforementioned private ECDSA key to access one of the other
machines, it doesn't work. I'm getting an error message instead:
$ ssh some-machine
key_from_blob: EC_KEY_new_by_curve_name failed
Worse, I can't even connect to other machines using an RSA key, even if
I change the remote authorized_keys file accordingly. The debug output
shows that in this case the connection attempt goes more or less
through, until the connection stops with the same message as above:
key_from_blob: EC_KEY_new_by_curve_name failed
The openssh ECDSA key format can't be different between different
versions of openssh, otherwise the keys wouldn't be usable on different
machines.
I also didn't see any bug reports that the new openssh version would not
be able to use ECDSA keys for some reason (ssh-keygen allows to create
new ECDSA keys, after all). If I revert to the vanilla openssh/openssl
versions, connecting via ECDSA key works as expected again.
Does anybody have an idea what the problem could be?
TIA,
Corinna
10 years, 5 months
dkms failure on reboot - virtualbox
by SternData
Booting after today's kernel update, I noticed that there was a dkms
failure:
Nov 17 10:08:10 sds-desk-2 vboxdrv[556]: Starting VirtualBox kernel
modules [FA
ILED]
Nov 17 10:08:10 sds-desk-2 vboxdrv[556]: (modprobe vboxdrv failed.
Please use '
dmesg' to find out why)
Nov 17 10:08:10 sds-desk-2 dkms_autoinstaller[558]: Starting dkms:
Error! Could not locate dkms.conf file.
Nov 17 10:08:10 sds-desk-2 dkms_autoinstaller[558]: File: does not exist.
# locate dkms.conf
/usr/share/virtualbox/src/vboxhost/dkms.conf
/var/lib/dkms/vboxhost/4.2.10/build/dkms.conf
/var/lib/dkms/vboxhost/4.2.18/build/dkms.conf
Does anyone else using the Oracle distribution of VirtualBox see any
errors after a kernel update?
--
-- Steve
10 years, 5 months
