03-15-2010
This patch is experimental and not included with the official ssh source code:
As before an unresolved problem with the multi-threaded AES-CTR routines forces us to release this as an experimental patch.
Not being as fast as it is with a different implementation isn't a bug so is unlikely covered by your support contract. It might be the case for a RFE though.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I am totally new to Unix. My current contract requires me to build an intranet site (nothing fancy, no forms, no cgi scripts, no search engine) for a unix platform.
I develop on an NT environment using dreamweaver.
I am considering buying Red Hat Linux, install that on the NT... (1 Reply)
Discussion started by: alam
1 Replies
2. IP Networking
I am trying to set an interface to 100/Full, but the command I use are getting rejected. I think it is the last argument, but I don't know how to find the correct values.
I am trying to use the following script, but change hme to le .
echo "Setting hme interface 1: 100mb/full-duplex..."
... (2 Replies)
Discussion started by: bbrandeb49
2 Replies
3. Solaris
Hi Guys,
I need help with ndd.
I was going through network FAQ but i have more questions then answers regarding ndd.
#ndd -set /dev/hme instance 0
#ndd -set /dev/hme adv_100fdx_cap 1
#ndd -set /dev/hme adv_100hdx_cap 0
#ndd -set /dev/hme adv_10fdx_cap 0
#ndd -set /dev/hme adv_10hdx_cap 0... (2 Replies)
Discussion started by: nitinkgoud
2 Replies
4. Solaris
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies
5. Solaris
Hi,
I would like to know whether there is any config file that i can refer to for the result of 'ndd -get /dev/tcp tcp_time_wait_interval'?
When i man 'ndd', there is one statement which is -> Each driver chooses which parameters to make visible using ndd. Does it answering my question above... (3 Replies)
Discussion started by: honmin
3 Replies
6. Solaris
Solaris 10 server (SunOS 5.10 Generic_137137_09)
I have a services file configured in /etc in there windows clients connect to my server on port 6034-6037
when I do the following
netstat | grep TestServices
it pulls all the connections active for those ports
so right now I have 10 clients... (3 Replies)
Discussion started by: deaconf19
3 Replies
7. SCO
While in SCO Openserver 5.0.7, Sybase listened to /dev/inet/tcp, the same is not working in SCO Openserver 6. The Network card is however active and pinging fine. What can be the reason? What is the way out?
An early response will be appreciated.
Thank you
Regards
TCG (2 Replies)
Discussion started by: thecobolguy
2 Replies
8. Red Hat
on RHEL 5.3 i did
mount -o remount,rw /dev/hda8 ( this is /tmp directory )
now OS not coming up.
How to resolve ??
---------- Post updated at 04:57 PM ---------- Previous update was at 03:36 PM ----------
one of my friend told me that you have changed sticky bit permissions on /tmp... (6 Replies)
Discussion started by: rehantayyab82
6 Replies
9. Solaris
Hello forum,
I have a Solaris 9 Sun Fire v240 server and Sun Fire v440
Recently we made changes and installed a new switch which both of them are connected to it. Cisco Catalyst 3750.
Now the Sun Server v240 is having problems with the network. It was supposed to run at 1000mbs speed.
ndd... (10 Replies)
Discussion started by: br1an
10 Replies
10. Shell Programming and Scripting
I have a command to check the status of hostname and port number,
echo > /dev/tcp/hostname/80
echo $?
0
success case
echo > /dev/tcp/hostname/809999
I got the output
-------------------
connection timed out
It took almost 4 minutes to time out,,, how can I set it to 10 seconds?
my... (2 Replies)
Discussion started by: sam@sam
2 Replies
LEARN ABOUT OSF1
shape_patch
SHAPE_PATCH(1) General Commands Manual SHAPE_PATCH(1)
NAME
shape_patch - shapeTools RMS generate patch file
SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>]
DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated
with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building
procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of
existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape
patch from the top node of the central source repository creates a patch file for the whole system.
The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH-
FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output.
Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure
will leave an equally named patch file for each visited subsystem.
The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1).
INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit.
SEE ALSO
shape_releas(1), vdiff(1), patch(1)
FILES
<name1>+2+<name2>.pat
13.10.119 SHAPE_PATCH(1)