Displaying 5 results from an estimated 5 matches for "accentr".
Did you mean:
accents
2005 May 16
1
Auslaenderpolitik (verification)
...----------------------------------------------
Below are the complete headers of the message that this email
was generated in response to.
Return-Path: <rsync@lists.samba.org>
Received: from lidswx.org (216-237-68-230-client.sopris.net [216.237.68.230] (may be forged))
by s85f54naa.servers.accentric.net (8.10.2/8.10.2) with SMTP id j4GHG2A26623;
Mon, 16 May 2005 10:16:03 -0700
From: rsync@lists.samba.org
To: StysSMTPchris@sagebrushlodge.com
Date: Mon, 16 May 2005 17:00:22 GMT
Subject: Auslaenderpolitik
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
MIME-Version: 1.0
Mes...
2006 Nov 01
0
No subject
...makes
it harder to find the few people in the crowd yelling "Hey, idiots..
upgrade! We are affected!"
However, in --current we did decide all fatal() calls should skip dealing
with zlib stuff and just exit. As a 'better safe then sorry' view.
- Ben
On Wed, 3 Apr 2002 dale at accentre.com wrote:
> On Wed, Apr 03, 2002 at 11:08:44AM -0600, Dave Dykstra wrote:
> > I'm disappointed that nobody has replied to my question. OpenSSH
> > development team, isn't the potential for a remote root exploit something
> > that's important to you? Many other...
2001 Jan 25
6
Distribution of openssh once compiled
Folks:
Thanks to all who helped me get ssh up and running on my development box.
Now I want to make a distribution package to take and install on the rest of
my network.
I am not sure what to transfer from box to box and what to run to get
started. I did
the install on the dev box and all tested fine.
Is there a "standard distribution" list of only files required for running
ssh on
2000 Nov 05
0
Socket options not properly set for ssh and sshd.
I'm sending this only to openssh-unix-dev at mindrot.org (since I'm using
the ported version of OpenSSH) and not to openssh at openssh.com, even
though I believe this to be a general problem. Please advise if you
think I should redirect this to the other mailing list.
Version: OpenSSH_2.2.0p1
Keywords: setsockopt keepalive hang masquerade
Symptom: For protocol 2, socket options
2001 Jan 12
0
Socket options not properly set for ssh and sshd.
I mentioned this problem in a previous post (in November). This time
I'm including a patch.
Version: OpenSSH_2.3.0p1
Keywords: setsockopt keepalive hang masquerade interactive
Symptom: For protocol 2, socket options (especially keepalive) are not
being properly set for OpenSSH_2.3.0p1, even when request in the config
files.
Furthermore (for either protocol), keepalive is only set for