Displaying 7 results from an estimated 7 matches for "cleaton".
Did you mean:
clean
2016 Apr 28
5
[Bug 11879] New: escape rrsync restricted folder
https://bugzilla.samba.org/show_bug.cgi?id=11879
Bug ID: 11879
Summary: escape rrsync restricted folder
Product: rsync
Version: 3.1.2
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee: wayned at samba.org
Reporter:
2003 Oct 12
0
idea (and patch): connection cookies
I have an idea for a protocol extension to limit the exposure of the
complex crypto code in ssh servers. It's like tcp-wrappers, but based
on a secret token rather than IP address.
Patch against openssh-3.7.1p2:
http://nick.cleaton.net/openssh-cc-0.03.patch
Details
=======
The "Connection Cookies" mechanism is an unofficial ssh protocol
extension designed to prevent attackers who are unable to packet sniff
legitimate sessions from exploiting future ssh server vulnerabilities.
The connection cookie is a shared sec...
2001 Jun 05
0
FreeBSD Security Advisory: FreeBSD-SA-01:40.fts
...eeBSD-SA-01:40 Security Advisory
FreeBSD, Inc.
Topic: fts(3) routines contain race condition
Category: core
Module: libc
Announced: 2001-06-04
Credits: Nick Cleaton <nick@cleaton.net>
Todd Miller <millert@openbsd.org> helped to develop the
patch.
Affects: FreeBSD 4.3-RELEASE, 4.3-STABLE prior to the correction
date.
Corrected: 2001-06-01
FreeBSD only: NO
I. Background
The standard C...
2001 Aug 16
0
FreeBSD Security Advisory FreeBSD-SA-01:40.fts [REVISED]
...Security Advisory
FreeBSD, Inc.
Topic: fts(3) routines contain race condition [REVISED]
Category: core
Module: libc
Announced: 2001-06-04
Revised: 2001-08-16
Credits: Nick Cleaton <nick@cleaton.net>
Todd Miller <millert@openbsd.org> helped to develop the
patch.
Affects: FreeBSD 4.3-RELEASE, 4.3-STABLE prior to the correction
date.
Corrected: 2001-06-01
FreeBSD only: NO
0. Revision History
2001-06-0...
2004 Sep 18
8
Attacks on ssh port
Hi,
Is there a security problem with ssh that I've missed???
Ik keep getting these hords of:
Failed password for root from 69.242.5.195 port 39239 ssh2
with all kinds of different source addresses.
They have a shot or 15 and then they are of again, but a little later on
they're back and keep clogging my logs.
Is there a "easy" way of getting these ip-numbers added to
2020 Feb 09
3
[draft PATCH] whitelist support for refuse options
This adds support for whitelisting the acceptable options in the
"refuse options" setting in rsyncd.conf. It introduces "!" as a
special option string that refuses most options and interprets
any following strings as patterns of options to allow.
For example, to allow only verbose and archive:
refuse options = ! verbose archive
The "!" does't refuse no-iconv,
2020 Feb 11
0
[draft PATCH] whitelist support for refuse options
..." directive) to be disallowed. Just a thought.
A potential problem with your approach I imagine is that it
would apply equally to all local users but different users
might have different use cases. The tools mentioned above
would support handling different users distinctly.
cheers,
raf
Nick Cleaton via rsync wrote:
> This adds support for whitelisting the acceptable options in the
> "refuse options" setting in rsyncd.conf. It introduces "!" as a
> special option string that refuses most options and interprets
> any following strings as patterns of options to a...