Sponsored Content
Special Forums Cybersecurity The Heartbleed Bug - What versions of the OpenSSL are affected? Post 302897300 by Neo on Sunday 13th of April 2014 12:40:27 AM
Old 04-13-2014
Also, you can test any server you use for the heartbleed bug at this excellent web site:

SSL Server Test
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

openssl help

I ungraded my openssl on sun solaris 8 from openssl 0.9.6c to openssl 0.9.6g the ungrade went fine but when I tried to ssh in to server, I received the following error message "ld.so.1: ./sshd: fatal: relocation error: file /usr/local/ssl/lib/libcrypto.so.0.9.6: symbol main: referenced symbol... (2 Replies)
Discussion started by: hassan2
2 Replies

2. Shell Programming and Scripting

check if a variable is not affected

Hi all, to check that a variable is not empty, I usually do: if ; then... or if ; then... what if I have a serie of variables and want to do the same test on all of them. How to do this in a single if statement? thank you (1 Reply)
Discussion started by: melanie_pfefer
1 Replies

3. What is on Your Mind?

Were You Affected by Volcanic Activity in Iceland?

If you were effected by the volcanic activity in Iceland, share you vote and story here. ---------- Post updated at 04:15 ---------- Previous update was at 04:10 ---------- A friend of mine in Tokyo had a contracting job with a film production company. They had to cancel an event because... (2 Replies)
Discussion started by: Neo
2 Replies

4. UNIX for Dummies Questions & Answers

Problem with FreeBSD 8.3. BIOS affected

Hello everybody. I have a problem of this kind: After installation of FreeBSD, my Windows XP became unreachable. Boot from CDROM is impossible. The conclusion: BIOS was damaged by GParted or some other program. Question: Are there any Unix means of updating (repairing) BIOS ?:wall: (11 Replies)
Discussion started by: prabux
11 Replies

5. AIX

High CPU Usage , users affected

Dear All, One production Server is affected by high usage. Application is slow now. Please guide me how to solve it? NMON Report shows full cpu usage. Here im posting some server details. bash-3.2# lparstat -i Node Name : ********* Partition Name ... (6 Replies)
Discussion started by: Thala
6 Replies

6. Cybersecurity

OpenSSL

I just started playing around with Unix's OpenSSL utility. I can't seem to get the hang of it, and the man page isn't helping much. I wanted to experiment with file encryption, so I created a dummy text file with one line of text and tried to encrypt it using DES. I used the following command: ... (2 Replies)
Discussion started by: Ultrix
2 Replies
Net::Server::Proto::SSL(3)				User Contributed Perl Documentation				Net::Server::Proto::SSL(3)

NAME
Net::Server::Proto::SSL - Net::Server SSL protocol. SYNOPSIS
See Net::Server::Proto. DESCRIPTION
Experimental. If anybody has any successes or ideas for improvment under SSL, please email <paul@seamons.com>. Protocol module for Net::Server. This module implements a secure socket layer over tcp (also known as SSL). See Net::Server::Proto. There is a limit inherent from using IO::Socket::SSL, namely that only one SSL connection can be maintained by Net::Server. However, Net::Server should also be able to maintain any number of TCP, UDP, or UNIX connections in addition to the one SSL connection. Additionally, getline support is very limited and writing directly to STDOUT will not work. This is entirely dependent upon the implementation of IO::Socket::SSL. getline may work but the client is not copied to STDOUT under SSL. It is suggested that clients sysread and syswrite to the client handle (located in $self->{server}->{client} or passed to the process_request subroutine as the first argument). PARAMETERS
In addition to the normal Net::Server parameters, any of the SSL parameters from IO::Socket::SSL may also be specified. See IO::Socket::SSL for information on setting this up. BUGS
Christopher A Bongaarts pointed out that if the SSL negotiation is slow then the server won't be accepting for that period of time (because the locking of accept is around both the socket accept and the SSL negotiation). This means that as it stands now the SSL implementation is susceptible to DOS attacks. To fix this will require deviding up the accept call a little bit more finely which may not yet be possible with IO::Socket::SSL. Any ideas or patches on this bug are welcome. LICENCE
Distributed under the same terms as Net::Server THANKS
Thanks to Vadim for pointing out the IO::Socket::SSL accept was returning objects blessed into the wrong class. perl v5.12.1 2007-02-03 Net::Server::Proto::SSL(3)
All times are GMT -4. The time now is 03:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy