Charles Hedrick wrote:
> In recent versions subdirectories called amd64 changed to just 64. This has
> caused no end of trouble.
There has been no such change. Since 64 bit support was first added to Solaris
x86 for Solaris 10, the convention has always been directories named amd64,
and symlink
I thought Android uses the Dalvik VM and not Java VM?
http://developer.android.com/guide/basics/what-is-android.html
based on this quote from the URL:
-
Android Runtime
Android includes a set of core libraries that provides most of the
functionality available in the core libraries of the Ja
I have seen this also, with older version of a certain popular Windows SSH
client which shall remain unnamed. It's surely a client problem. The only
potential flaw on the server's side is that it's not giving you a more
"human-friendly" error message. But, really, it shouldn't have to. Your clie
In recent versions subdirectories called amd64 changed to just 64. This has
caused no end of trouble. X will probably start with no /etc/X11/xorg.conf, or
you can update the directory names in the file, or you can add symlinks between
amd64 and 64 everywhere.
Also, things were moved from someth
I assure you it is ssh2 and is set for des. normally 3des is the default.
none of the other available Ciphers work, when i tried to edit the config
file and restart ssh it crashed, went into maintainence mode and refused to
start. Not sure if the Ciphers line has to go at a specific spot in th
yah, that's it. I guess this will be fixed in a later release then. It's
not critical, just really annoying.
On Sun, Feb 7, 2010 at 11:58 AM, Alan Coopersmith
wrote:
> Thomas Burgess wrote:
> > I've noticed something strange with solaris i've never seen with any
> other os.
> >
> > I use ssh f
it makes sense but when i tried to enable the cipers in the config file ssh
refused to start and stayed in maintainence mode. It took me 20 minutes 2
reboots and 20 commands to get it to start back upthis is really
frustrating.
I'd rather just have OpenSSH
oh well
I'll try again i guess
On 02/ 7/10 12:57 PM, Thomas Burgess wrote:
I just started using send/receive myself yesterday.
This is what i found out
I wanted to do the same thing, i had a filesystem called Video in my
tank pool, it looked like this:
tank/nas/Video (pool was tank, it was a child of nas) and it was
moun
The error message is the client telling you that DES isn't a supported
cipher. That's not an issue with anyone's SSH as you seem to suggest–
it's the client telling you that a choice that's outside the protocol
spec can't be accepted.
Thus far the evidence is that you're working backwards fr
You shouldn't be able to use des at all if you're using v2 of the
protocol. Perhaps the problem isn't your choice of ciphers but using
ssh v1 or setting ciphers for the wrong version?
Using iTerm allows you to use the native ssh client so that you don't
have to fiddle with these settings in
The cbc cyphers are not enabled by default because all of them have been broken:
https://www.kb.cert.org/vuls/id/958563
the default cypher-list is:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,arcfour
I'm not sure why it didn't go with arcfour, but I would strongly recommend
upgradin
> I normally use JellyFiSSH as my ssh tool on osx, and with every other os,
> it has no problems with any of the ssh encryption protocols. The default
> is 3des but it has many to chose from (blowfish, 3des-cbc, cast128-cbc,
> blowfish-cbc, arcfour, aes256-cbc)
>
> OpenSolaris doesn't allow me to
Thomas Burgess wrote:
> I've noticed something strange with solaris i've never seen with any other os.
>
> I use ssh for my terminal. Most of my work in opensolaris is done in this
> way. Whenever i use nano, when i close/save the file i'm working on, the
> entire shell starts highlinging ever
I normally use JellyFiSSH as my ssh tool on osx, and with every other os, it
has no problems with any of the ssh encryption protocols. The default is 3des
but it has many to chose from (blowfish, 3des-cbc, cast128-cbc, blowfish-cbc,
arcfour, aes256-cbc)
OpenSolaris doesn't allow me to use ANY
Same problem here, very annoying.
Plus a problem getting emacs white background, it is grey as you sait by
default even if I have the white backgound in .emacs, I can force it to be
lightyelloy by using -bg white, but for real white, nope !
It's not lethal, but these daily/hourly annoyances are a
I've noticed something strange with solaris i've never seen with any other os.
I use ssh for my terminal. Most of my work in opensolaris is done in this way.
Whenever i use nano, when i close/save the file i'm working on, the entire
shell starts highlinging everthing grey.
This also seems to
16 matches
Mail list logo
