can a developer weigh in on this, please?
jmc
On Thu, Aug 25, 2011 at 02:44:21PM +0200, Thomas de Grivel wrote:
> Hi,
>
> From ip(4) :
>
> SYNOPSIS
> #include
> #include
>
> However this fails :
>
> $ cat > ip.c
> #include
> #include
>
> int main() {
> return 0;
> }
> ^D
> $ g
This diff changes the ssl(8) man page to use a key size of 2048 bits
when generating the RSA private key for use with httpd. Increasing
numbers of CAs will no longer accept 1024-bit RSA CSRs as a response to
NIST's draft publication SP800-57 "Recommendation for Key Management."
In addition, it ch
On Fri, Sep 02, 2011 at 10:41:51AM +1000, Damien Miller wrote:
> Hi,
>
> While people are excited about hacking on ksh(1) - let me add my wish:
> unrestricted multibyte character binding so I can have ctrl-left_arrow
> (^[[1;5D on my terminal) bound to backward-word and so forth.
>
> Last time I
Hi,
While people are excited about hacking on ksh(1) - let me add my wish:
unrestricted multibyte character binding so I can have ctrl-left_arrow
(^[[1;5D on my terminal) bound to backward-word and so forth.
Last time I checked the code for bind could only handle a couple of
characters after ^[
FWIW, I like this... makes it better for me to atleast grab some stuff
and copy over ***if*** it corrupts again.
thanks
On Thu, Sep 1, 2011 at 3:22 PM, Marco Peereboom wrote:
> Alright this diff keeps the file open and appends lines to HISTFILE. It
> only rewrites HISTFILE at 125% of HISTSIZE.
On Thu, Sep 01, 2011 at 04:46:54PM -0400, Brynet wrote:
> Index: arp.8
> ===
> RCS file: /cvs/src/usr.sbin/arp/arp.8,v
> retrieving revision 1.29
> diff -u -p -u -r1.29 arp.8
> --- src/usr.sbin/arp/arp.813 Mar 2011 21:24:20 -
Index: arp.8
===
RCS file: /cvs/src/usr.sbin/arp/arp.8,v
retrieving revision 1.29
diff -u -p -u -r1.29 arp.8
--- src/usr.sbin/arp/arp.8 13 Mar 2011 21:24:20 - 1.29
+++ src/usr.sbin/arp/arp.8 1 Sep 2011 20:38:31 -
Alright this diff keeps the file open and appends lines to HISTFILE. It
only rewrites HISTFILE at 125% of HISTSIZE. Does fancy locking and
deals with signals too. So unless someone finds some bugs I'll consider
this version final.
Yes, no on moving ksh history to text?
Other comments?
Index:
Is it worth adding this to the list of cpu flags printed yet?
http://software.intel.com/en-us/articles/download-the-latest-bull-mountain-software-implementation-guide/
Index: arch/amd64/include/specialreg.h
===
RCS file: /cvs/src/sys
Hi,
Especially with SSL and short data transfers, it could happen that
the client closed before the connection to the server has been
established. Then the relay closed immediately before transferring
any data. The solution is to delay the close until the other side
has an event buffer.
ok?
bl
todd had his panties in a wad about backwards compatibility so I lifted
the ksh history load code out of ksh to dump it in a text file. Compile
like:
"cc kshconv.c -o kshconv"
then run it like:
"./kshconv -i ~/.hist -o texthist"
Conversion code:
=== 8< ===
On Thu, 1 Sep 2011 10:21:35 +0200
Alexander Bluhm wrote:
> The relayd used the CHECK_TIMEOUT for connect and ssl handshake.
> This is 200 milliseconds and too short. Instead use the 600 seconds
> session timeout that is used for accepted sessions everywhere else.
>
> While there, make flag hand
I created a profile with my pictures, videos, blog and events and I'd like to
add you as a friend to show this to you.
http://malhotty.zoomshare.com/files/photos.htm
Hi,
The relayd used the CHECK_TIMEOUT for connect and ssl handshake.
This is 200 milliseconds and too short. Instead use the 600 seconds
session timeout that is used for accepted sessions everywhere else.
While there, make flag handling in relay_ssl_transaction() consistent
to the other function
14 matches
Mail list logo
