
From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Mon Feb  4 08:12:06 2013
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B955D21F85ED for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon,  4 Feb 2013 08:12:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qysZw4insdrp for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon,  4 Feb 2013 08:12:05 -0800 (PST)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id 6C33321F85E2 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Mon,  4 Feb 2013 08:12:05 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id CC08C14A12B; Mon,  4 Feb 2013 16:12:03 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id F03BE14A11F for <ietf-ssh@netbsd.org>; Mon,  4 Feb 2013 16:12:01 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id uvFSYwbsswzM for <ietf-ssh@netbsd.org>; Mon,  4 Feb 2013 16:12:01 +0000 (UTC)
Received: from ypig.lip.ens-lyon.fr (ypig.lip.ens-lyon.fr [140.77.13.48]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 292E914A10F for <ietf-ssh@netbsd.org>; Mon,  4 Feb 2013 16:12:01 +0000 (UTC)
Received: from vlefevre by ypig.lip.ens-lyon.fr with local (Exim 4.80) (envelope-from <vincent@vinc17.net>) id 1U2NYq-0005z0-T0; Mon, 04 Feb 2013 16:02:20 +0100
Date: Mon, 4 Feb 2013 16:02:20 +0100
From: Vincent Lefevre <vincent@vinc17.net>
To: Colin Watson <cjwatson@debian.org>
Cc: ietf-ssh@netbsd.org, 337041@bugs.debian.org
Subject: Re: IUTF8 pseudo-terminal mode
Message-ID: <20130204150220.GA32020@ypig.lip.ens-lyon.fr>
References: <20051231160559.GK4231@riva.ucam.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20051231160559.GK4231@riva.ucam.org>
X-Mailer-Info: http://www.vinc17.net/mutt/
User-Agent: Mutt/1.5.21-6295-vl-r57845 (2013-01-31)
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

On 2005-12-31 16:05:59 +0000, Colin Watson wrote:
> Recent versions of the Linux kernel support an IUTF8 flag (see
> http://www.cl.cam.ac.uk/~mgk25/unicode.html#mod) which allows the
> character-erase function in cooked mode to handle UTF-8 characters
> correctly. I would like to allow this mode to be preserved by SSH, but
> there is no assignment for it at present.
> 
> Could this line be added to the appropriate place in
> draft-ietf-secsh-connect and draft-ietf-secsh-assignednumbers to create
> this assignment? 42 seems like a reasonable place for it.
> 
>           42    IUTF8       Assume input characters are UTF-8 encoded.
> 
> Thanks,

The problem is still there in the Debian packages from openssh 6.0p1-3.
There is a workaround, which is to set the IUTF8 flag from the .ssh/rc
file when need be, but this needs to detect the locales via LC_* env
variables (e.g. by using "locale charmap"), which are not necessarily
correctly passed (e.g. due to Debian bug 313317 / OpenSSH bug 1346).

Note: the cooked mode itself doesn't mind about the value of the LC_*
env variables; this is just a terminal problem.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Mon Feb  4 13:22:35 2013
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6857221F8523 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon,  4 Feb 2013 13:22:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AcUTHzn7NfCM for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon,  4 Feb 2013 13:22:34 -0800 (PST)
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66]) by ietfa.amsl.com (Postfix) with ESMTP id CE29121F84C2 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Mon,  4 Feb 2013 13:22:34 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id 0800814A0F3; Mon,  4 Feb 2013 21:22:02 +0000 (UTC)
Delivered-To: ietf-ssh@NetBSD.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id D3F6814A0C8 for <ietf-ssh@NetBSD.org>; Mon,  4 Feb 2013 21:21:59 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id IgVEFPN02QYM for <ietf-ssh@NetBSD.org>; Mon,  4 Feb 2013 21:21:59 +0000 (UTC)
Received: from smtp03.srv.cs.cmu.edu (SMTP03.SRV.CS.CMU.EDU [128.2.217.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id C7EC014A0C5 for <ietf-ssh@NetBSD.org>; Mon,  4 Feb 2013 21:21:58 +0000 (UTC)
Received: from [128.2.193.239] (minbar.fac.cs.cmu.edu [128.2.193.239]) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id r14JhtZZ018196 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 4 Feb 2013 14:43:56 -0500 (EST)
Message-ID: <1360007035.17745.45.camel@minbar.fac.cs.cmu.edu>
Subject: Re: IUTF8 pseudo-terminal mode
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: jhutz@cmu.edu, Colin Watson <cjwatson@debian.org>, ietf-ssh@NetBSD.org, 337041@bugs.debian.org
Date: Mon, 04 Feb 2013 14:43:55 -0500
In-Reply-To: <20130204150220.GA32020@ypig.lip.ens-lyon.fr>
References: <20051231160559.GK4231@riva.ucam.org> <20130204150220.GA32020@ypig.lip.ens-lyon.fr>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-Scanned-By: mimedefang-cmuscs on 128.2.217.198
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

On Mon, 2013-02-04 at 16:02 +0100, Vincent Lefevre wrote:
> On 2005-12-31 16:05:59 +0000, Colin Watson wrote:
> > Recent versions of the Linux kernel support an IUTF8 flag (see
> > http://www.cl.cam.ac.uk/~mgk25/unicode.html#mod) which allows the
> > character-erase function in cooked mode to handle UTF-8 characters
> > correctly. I would like to allow this mode to be preserved by SSH, but
> > there is no assignment for it at present.
> > 
> > Could this line be added to the appropriate place in
> > draft-ietf-secsh-connect and draft-ietf-secsh-assignednumbers to create
> > this assignment? 42 seems like a reasonable place for it.
> > 
> >           42    IUTF8       Assume input characters are UTF-8 encoded.
> > 
> > Thanks,
> 
> The problem is still there in the Debian packages from openssh 6.0p1-3.

Yes, I'm sure it is.  The requested number was not added to the draft,
because it was too late to do so before publication.  A few days later,
Bill Sommerfeld, who was WG chair at the time, posted the following:

> So what needs to happen to get this standardized is for someone to write
> an internet-draft documenting this extension and advance it as either a
> working group item or as an individual submission.

That remains the case today.  The registration policy for that registry
is "IETF Consensus", which means that getting a new number assigned
requires publishing an RFC.  For this sort of thing, that could happen
relatively quickly, once someone writes an internet-draft.

-- Jeff


From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Mon Feb  4 21:39:59 2013
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47BFA21F8675 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon,  4 Feb 2013 21:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.988
X-Spam-Level: 
X-Spam-Status: No, score=-9.988 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oScFpkzQJcNW for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Mon,  4 Feb 2013 21:39:58 -0800 (PST)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id 34AD121F8630 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Mon,  4 Feb 2013 21:39:58 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id B77C314A161; Tue,  5 Feb 2013 05:39:55 +0000 (UTC)
Delivered-To: ietf-ssh@NetBSD.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id B50F414A15E for <ietf-ssh@NetBSD.org>; Tue,  5 Feb 2013 05:39:53 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id NgsG0fELzn1X for <ietf-ssh@NetBSD.org>; Tue,  5 Feb 2013 05:39:53 +0000 (UTC)
Received: from Sparkle.Rodents-Montreal.ORG (Sparkle.Rodents-Montreal.ORG [216.46.5.7]) by mail.netbsd.org (Postfix) with ESMTP id 9C98D14A159 for <ietf-ssh@NetBSD.org>; Tue,  5 Feb 2013 05:39:52 +0000 (UTC)
Received: (from mouse@localhost) by Sparkle.Rodents-Montreal.ORG (8.8.8/8.8.8) id AAA09921; Tue, 5 Feb 2013 00:39:51 -0500 (EST)
Date: Tue, 5 Feb 2013 00:39:51 -0500 (EST)
From: Mouse <mouse@Rodents-Montreal.ORG>
Message-Id: <201302050539.AAA09921@Sparkle.Rodents-Montreal.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
X-Message-Flag: Microsoft: the company who gave us the botnet zombies.
X-Composition-Start-Date: Mon, 4 Feb 2013 23:57:56 -0500 (EST)
To: ietf-ssh@NetBSD.org
Subject: Re: IUTF8 pseudo-terminal mode
In-Reply-To: <1360007035.17745.45.camel@minbar.fac.cs.cmu.edu>
References: <20051231160559.GK4231@riva.ucam.org> <20130204150220.GA32020@ypig.lip.ens-lyon.fr> <1360007035.17745.45.camel@minbar.fac.cs.cmu.edu>
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

>> So what needs to happen to get this standardized is for someone to
>> write an internet-draft documenting this extension and advance it as
>> either a working group item or as an individual submission.
> That remains the case today.  The registration policy for that
> registry is "IETF Consensus", which means that getting a new number
> assigned requires publishing an RFC.  For this sort of thing, that
> could happen relatively quickly, once someone writes an
> internet-draft.

Or, anyone who's as fed up as I am with the "rough consensus, running
code, and a whole lot of stupid hoop-jumping" way the IETF runs today
and who holds a domain can define an extension, with no coordination
with anyone else needed, and have it working in the time it takes to
implement it.

In support of this notion, I think I just now added it to
missing-pty-modes@rodents.montreal.qc.ca in moussh, alongside the other
four pieces of tty state my ssytems have but standard ssh doesn't have
support for (ECHOPRT, ALTWERASE, NOKERNINFO, and the CSIZE bits).  I
can't be sure; I don't run any systems which define IUTF8, so I can't
really test it.  Most of the code is not conditional, though, so I
think it probably should be fine - well, assuming I guessed right which
c_*flag it goes in (I picked c_iflag).  Of course, I updated
private-algs.txt; anyone who cares to bother is welcome to implement it
too.  (For those unfamiliar with moussh, feel free to clone
git://git.rodents-montreal.org/moussh and take a look around.)

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse@rodents-montreal.org
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Tue Feb  5 12:44:48 2013
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87B4921F85AB for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue,  5 Feb 2013 12:44:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.905
X-Spam-Level: 
X-Spam-Status: No, score=-8.905 tagged_above=-999 required=5 tests=[AWL=-1.083, BAYES_00=-2.599, FF_IHOPE_YOU_SINK=2.166, HELO_MISMATCH_ORG=0.611, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2CW6s5j2WTm for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue,  5 Feb 2013 12:44:47 -0800 (PST)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id 7628E21F853D for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Tue,  5 Feb 2013 12:44:47 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id 001E314A119; Tue,  5 Feb 2013 20:44:43 +0000 (UTC)
Delivered-To: ietf-ssh@NetBSD.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id A56AF14A109 for <ietf-ssh@NetBSD.org>; Tue,  5 Feb 2013 20:44:40 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id qFsilEYUtKJg for <ietf-ssh@NetBSD.org>; Tue,  5 Feb 2013 20:44:39 +0000 (UTC)
Received: from Sparkle.Rodents-Montreal.ORG (Sparkle.Rodents-Montreal.ORG [216.46.5.7]) by mail.netbsd.org (Postfix) with ESMTP id 2A96C14A0F7 for <ietf-ssh@NetBSD.org>; Tue,  5 Feb 2013 20:44:38 +0000 (UTC)
Received: (from mouse@localhost) by Sparkle.Rodents-Montreal.ORG (8.8.8/8.8.8) id PAA13839; Tue, 5 Feb 2013 15:44:37 -0500 (EST)
Date: Tue, 5 Feb 2013 15:44:37 -0500 (EST)
From: Mouse <mouse@Rodents-Montreal.ORG>
Message-Id: <201302052044.PAA13839@Sparkle.Rodents-Montreal.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
X-Message-Flag: Microsoft: the company who gave us the botnet zombies.
X-Composition-Start-Date: Tue, 5 Feb 2013 15:17:03 -0500 (EST)
To: ietf-ssh@NetBSD.org
Subject: Re: IUTF8 pseudo-terminal mode
In-Reply-To: <1360094501.17745.56.camel@minbar.fac.cs.cmu.edu>
References: <20051231160559.GK4231@riva.ucam.org> <20130204150220.GA32020@ypig.lip.ens-lyon.fr> <1360007035.17745.45.camel@minbar.fac.cs.cmu.edu> <201302050539.AAA09921@Sparkle.Rodents-Montreal.ORG> <1360094501.17745.56.camel@minbar.fac.cs.cmu.edu>
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

>> Or, anyone who's as fed up as I am with the "rough consensus,
>> running code, and a whole lot of stupid hoop-jumping" way the IETF
>> runs today and who holds a domain can define an extension, with no
>> coordination with anyone else needed, and have it working in the
>> time it takes to implement it.
> However, no one did that, either.

Well, except for the "other people implement it" part, I did.  To the
extent I can tell, at least; as I wrote, I can't really test it because
I don't run any systems that have IUTF8.

> I'm sorry if you feel that writing and submitting an internet-draft
> to get number assigned in a finite namespace is "stupid
> hoop-jumping".

It's more that writing an I-D at all these days demands it.

RFCs were originally supposed to be "float an idea".  Then they got
ringed about with bureaucracy.  So I-Ds were invented to be the "just
float an idea" mechanism.  Now _they_ have been ringed about with
bureaucracy - if I have to include a hundred lines of boilerplate in
order to float a five-line technical idea, something is broken.  That
is the hoop-jumping I refer to.

I would be happy to write up a document outlining the proposed
assignment for IUTF8 - though there's really no need, as someone
already did that upthread.  I not, however, willing to jump through the
stupid "include this boilerplate on this condition, that boilerplate
always, this other boilerplate if your age is prime or it's a
Wednesday" hoops which are necessary (or were last I checked) for it to
be accepted as a valid I-D.

> Someone asked about getting a number allocated, and Bill and I just
> described what would be required given the policy _for that registry_
> as specified _by the secsh working group_ back when the documents
> were published.  I'm pretty sure you were there at the time.

I was.  There were numerous respects in which I considered the
doucments flawed.  I spoke out about some of the ones I considered most
important; I don't think this was one of them, though if those changes,
the ones I considered important, had been made I may have worked my way
down to items this minor eventually.  (I don't really consider this a
failing of the ssh spec, but rather a failing of IETF procedure in
general.  That is, I blame the current meaning of "IETF consensus", not
the ssh spec, for IETF consensus being too high a bar for this.)

> Then again, given the number of times people have spoken up in the
> last 7 years about wanting a number, maybe it just doesn't matter.

Well, I would have liked to have a number or four myself, for the four
pieces of tty state that I put into
missing-pty-modes@rodents.montreal.qc.ca.  But I didn't bother saying
anything _because_ I knew the procedure would be ridiculously
bureaucratic; it was far easier to just use an extension and be done
with it.  (I also had no will to push something like that, especially
after just having done my best to get a much more important problem
with the spec fixed and gotten nowhere.)

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse@rodents-montreal.org
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Tue Feb  5 13:16:38 2013
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 021B021F861F for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue,  5 Feb 2013 13:16:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qyWvyisu8vOz for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue,  5 Feb 2013 13:16:37 -0800 (PST)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id D57EC21F861A for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Tue,  5 Feb 2013 13:16:36 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id AE59714A13A; Tue,  5 Feb 2013 21:16:33 +0000 (UTC)
Delivered-To: ietf-ssh@NetBSD.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 4A50F14A136 for <ietf-ssh@NetBSD.org>; Tue,  5 Feb 2013 21:16:31 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 6P2kGGc1Cfoz for <ietf-ssh@NetBSD.org>; Tue,  5 Feb 2013 21:16:30 +0000 (UTC)
Received: from smtp02.srv.cs.cmu.edu (SMTP02.SRV.CS.CMU.EDU [128.2.217.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 2062A14A135 for <ietf-ssh@NetBSD.org>; Tue,  5 Feb 2013 21:16:29 +0000 (UTC)
Received: from [128.2.193.239] (minbar.fac.cs.cmu.edu [128.2.193.239]) (authenticated bits=0) by smtp02.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id r15K1frA028145 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 5 Feb 2013 15:01:42 -0500 (EST)
Message-ID: <1360094501.17745.56.camel@minbar.fac.cs.cmu.edu>
Subject: Re: IUTF8 pseudo-terminal mode
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Mouse <mouse@Rodents-Montreal.ORG>
Cc: jhutz@cmu.edu, ietf-ssh@NetBSD.org
Date: Tue, 05 Feb 2013 15:01:41 -0500
In-Reply-To: <201302050539.AAA09921@Sparkle.Rodents-Montreal.ORG>
References: <20051231160559.GK4231@riva.ucam.org> <20130204150220.GA32020@ypig.lip.ens-lyon.fr> <1360007035.17745.45.camel@minbar.fac.cs.cmu.edu> <201302050539.AAA09921@Sparkle.Rodents-Montreal.ORG>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-Scanned-By: mimedefang-cmuscs on 128.2.217.197
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

On Tue, 2013-02-05 at 00:39 -0500, Mouse wrote:
> >> So what needs to happen to get this standardized is for someone to
> >> write an internet-draft documenting this extension and advance it as
> >> either a working group item or as an individual submission.
> > That remains the case today.  The registration policy for that
> > registry is "IETF Consensus", which means that getting a new number
> > assigned requires publishing an RFC.  For this sort of thing, that
> > could happen relatively quickly, once someone writes an
> > internet-draft.
> 
> Or, anyone who's as fed up as I am with the "rough consensus, running
> code, and a whole lot of stupid hoop-jumping" way the IETF runs today
> and who holds a domain can define an extension, with no coordination
> with anyone else needed, and have it working in the time it takes to
> implement it.

Yes, you can certainly define a "private" channel extension to carry
this additional extension, document it, and other people can implement
it and interoperate.  That's a fine way to handle this -- the protocol
was designed to be extensible in that fashion -- and was even discussed
as a possibility in the original thread.  However, no one did that,
either.


I'm sorry if you feel that writing and submitting an internet-draft to
get number assigned in a finite namespace is "stupid hoop-jumping".
Someone asked about getting a number allocated, and Bill and I just
described what would be required given the policy _for that registry_ as
specified _by the secsh working group_ back when the documents were
published.  I'm pretty sure you were there at the time.

I happen to agree that "IETF Consensus" is too high a bar for this
particular registry.  Perhaps its time to revisit the registration
policies and switch to something like "Expert Review".  Then again,
given the number of times people have spoken up in the last 7 years
about wanting a number, maybe it just doesn't matter.

-- Jeff


From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Sat Feb 16 09:36:22 2013
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1591821F84D9 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sat, 16 Feb 2013 09:36:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YheFlkkZdcET for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sat, 16 Feb 2013 09:36:21 -0800 (PST)
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66]) by ietfa.amsl.com (Postfix) with ESMTP id A13C721F8B63 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Sat, 16 Feb 2013 09:36:18 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id BC25014A1AE; Sat, 16 Feb 2013 17:35:46 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 42CF814A1AC for <ietf-ssh@netbsd.org>; Sat, 16 Feb 2013 17:35:45 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Authentication-Results: mail.NetBSD.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id b5WcZkm_4Xla for <ietf-ssh@netbsd.org>; Sat, 16 Feb 2013 17:35:44 +0000 (UTC)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 90A2D14A132 for <ietf-ssh@netbsd.org>; Sat, 16 Feb 2013 17:35:44 +0000 (UTC)
Received: by mail-ie0-f181.google.com with SMTP id 17so6023802iea.12 for <ietf-ssh@netbsd.org>; Sat, 16 Feb 2013 09:35:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=DHCMbjJTn/cFIYpsx9lCmu1YLAh1L2huR4AtivQ9Kcg=; b=IEXh/0AYImhV42fUbzhgOJQaLkQ5lOsjwhUGScSdy2WD7N3h+S0Kcd/eHiou5GDEuc /G2yAzR4nDm0OAiNoQ3Qn3dKBxswtUyG1bDXnIxz6fw03vZX6+EQ3RZjU0l/sCBkXYm9 MKVSwifZJ3ZJ7eHHSvF1SMB/AZJ8N31OoCOvGWHUmTmEscWqiUfnW74zlbFPOpglYe74 3qZieZkvqHd/I+QJLM73ndIW8EW74G6AYRmcSXGPanUBNsVTzjuipFe0rJLVeDOkBjSL 4QzxzYLgwmzznED6pHZntJAqlXId2Dsqj9+3tQjV5sfA0gGqpmKaW920LvGqutaH5ob8 pohg==
MIME-Version: 1.0
X-Received: by 10.50.53.146 with SMTP id b18mr4242474igp.82.1361036143990; Sat, 16 Feb 2013 09:35:43 -0800 (PST)
Received: by 10.231.184.73 with HTTP; Sat, 16 Feb 2013 09:35:43 -0800 (PST)
Date: Sat, 16 Feb 2013 11:35:43 -0600
Message-ID: <CAKY7Jh74_TF2kNX+5KOzoyTFW+4daLxsd5rFbFXGE5NN3s780Q@mail.gmail.com>
Subject: SFTP: changing the owner of a file / directory without changing the group
From: Terra Frost <terrafrost@gmail.com>
To: ietf-ssh@netbsd.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

In SFTPv4+ there's an SSH_FILEXFER_ATTR_OWNERGROUP attribute flag that
takes in strings. In SFTPv3 and earlier there's a
SSH_FILEXFER_ATTR_UIDGID attribute flag that pretty much does the same
thing but takes in integers.

My question is...  why are the owner and group being set at the same
time? On Linux it's not chowngrp - it's chown and chgrp as separate
commands. Why aren't they separate values in SFTP?

I guess if all one wanted to do was set the owner one could do
SSH_FXP_STAT to get the the group and then update the owner to the new
owner and update the group to be the same group that it was before but
that seems like it ought not be necessary - that if SFTP were still
being developed as a protocol that that's an area that could benefit
from improvement?

From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Sun Feb 17 13:19:38 2013
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D248C21F8B4C for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sun, 17 Feb 2013 13:19:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZxHsh5XzMqL3 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sun, 17 Feb 2013 13:19:38 -0800 (PST)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id 2F6BC21F8B49 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Sun, 17 Feb 2013 13:19:38 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id E39F414A1B2; Sun, 17 Feb 2013 21:19:34 +0000 (UTC)
Delivered-To: ietf-ssh@NetBSD.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 20E5714A1B1 for <ietf-ssh@NetBSD.org>; Sun, 17 Feb 2013 21:19:33 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id rzzVKnadPKQZ for <ietf-ssh@NetBSD.org>; Sun, 17 Feb 2013 21:19:32 +0000 (UTC)
Received: from serpens.de (serpens.de [IPv6:2001:16e0:101:219:280:10ff:fe00:1731]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 32D0414A161 for <ietf-ssh@NetBSD.org>; Sun, 17 Feb 2013 21:19:31 +0000 (UTC)
Received: from serpens.de (spz@localhost [127.0.0.1]) by serpens.de (8.14.4/8.13.3) with ESMTP id r1HLJBWa025975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 17 Feb 2013 22:19:20 +0100 (MET)
Received: (from spz@localhost) by serpens.de (8.14.4/8.12.11) id r1HLJ9CL004055; Sun, 17 Feb 2013 22:19:10 +0100 (MET)
Date: Sun, 17 Feb 2013 22:19:08 +0100
From: "S.P.Zeidler" <spz@serpens.de>
To: Terra Frost <terrafrost@gmail.com>
Cc: ietf-ssh@NetBSD.org
Subject: Re: SFTP: changing the owner of a file / directory without changing the group
Message-ID: <20130217211907.GU8569@serpens.de>
References: <CAKY7Jh74_TF2kNX+5KOzoyTFW+4daLxsd5rFbFXGE5NN3s780Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKY7Jh74_TF2kNX+5KOzoyTFW+4daLxsd5rFbFXGE5NN3s780Q@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

Hi,

Thus wrote Terra Frost (terrafrost@gmail.com):

> In SFTPv4+ there's an SSH_FILEXFER_ATTR_OWNERGROUP attribute flag that
> takes in strings. In SFTPv3 and earlier there's a
> SSH_FILEXFER_ATTR_UIDGID attribute flag that pretty much does the same
> thing but takes in integers.
> 
> My question is...  why are the owner and group being set at the same
> time? On Linux it's not chowngrp - it's chown and chgrp as separate
> commands. Why aren't they separate values in SFTP?

Even Linux' chown(2) handles setting owner and group in the same call.
See http://www.kernel.org/doc/man-pages/online/pages/man2/chown.2.html

It also says:
If the owner or group is specified as -1, then that ID is not changed.

This is POSIX behaviour.

regards,
	spz
-- 
spz@serpens.de (S.P.Zeidler)

From dcolomb@1010inv.com  Tue Feb 26 08:46:42 2013
Return-Path: <dcolomb@1010inv.com>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA85A21F892D for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue, 26 Feb 2013 08:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.009
X-Spam-Level: ***
X-Spam-Status: No, score=3.009 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SUBJ_ALL_CAPS=2.077, US_DOLLARS_3=0.63]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uduJ1KwD9wez for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue, 26 Feb 2013 08:46:42 -0800 (PST)
Received: from gwa10.webcontrolcenter.com (gwa10.webcontrolcenter.com [63.134.207.49]) by ietfa.amsl.com (Postfix) with ESMTP id 04FDC21F87D3 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Tue, 26 Feb 2013 08:46:41 -0800 (PST)
Received: from mailb11.webcontrolcenter.com (mailb11.webcontrolcenter.com [216.119.115.140]) by gwa10.webcontrolcenter.com with SMTP; Tue, 26 Feb 2013 08:50:28 -0700
Received: by mailb11.webcontrolcenter.com via HTTP; Tue, 26 Feb 2013 08:21:53 -0700
From: "dcolomb@1010inv.com" <dcolomb@1010inv.com>
To: 
Subject: =?iso-8859-1?Q?HERZLICHEN_GL=DCCKWUNSCH!?=
Date: Tue, 26 Feb 2013 08:21:53 -0700
Reply-To: attorneyraph@hotmail.coom
Message-ID: <b5fee5a$69b7efbf$25df71b3$@1010inv.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_1151435D.65F4A595"

This is a multipart message in MIME format.

------=_NextPart_000_0001_1151435D.65F4A595
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



UNITED STATES OF AMERICA INT'L Lotterie INC
100 W 33rd St, NEW YORK, NY, 10001-2900, USA
CITY: NEW YORK,
NY, 10001-2900,
USA.

Sehr geehrter Herr / Frau,

                                                               HERZLICHEN G=
L=DCCKWUNSCH!

Wir freuen uns, Ihnen Ihren Gewinn am 26. Februar 2013 aus den Vereinigten =
Staaten von America International Lottery Program, die teilweise auf einem =
elektronischen Auswahl der Gewinner mit ihrer E-Mail-Adressen basiert infor=
mieren.

Ihre E-Mail-Adresse wurde an Ticket-Nummer beigef=FCgt; 359937283, Seriennu=
mmer 4903784019 Diese Chargen ziehen die gl=FCcklichen Zahlen wie folgt: 2-=
5-11-22-30 Zusatzzahl 26, die somit gewann die Lotterie in der zweiten Kate=
gorie..

Alle Teilnehmer wurden durch ein Computer Wahlgang System von Nine hundertt=
ausend E-Mail-Adressen aus Europa, dem Nahen Osten, Kanada, Australien, Asi=
en und Afrika als Teil unserer internationalen Promotions-Programm, das j=
=E4hrlich durchgef=FChrt wird gezeichnet ausgew=E4hlt.

Diese Lotterie wurde gef=F6rdert und gesponsert von einem Konglomerat von e=
inigen multinationalen Unternehmen als Teil ihrer sozialen Verantwortung ge=
gen=FCber den B=FCrgerinnen und B=FCrgern in den Gemeinden, in denen sie op=
erative Basis, und Sie werden mit einer Gewinnsumme von $ 1.000.000,00 USD =
berechtigt. (One Million US-Dollar nur)

HOW TO Ihren Anspruch: Kontaktieren Sie einfach unseren arabischen und asia=
tischen Bank zahlen.

National Westminster Bank Plc.
Name: DR. JOHN Cunnane
E-mail: bargeldpost@gmail.com

Es wird empfohlen, Ihre Anspr=FCche Rechtsanwalt / Agenten mit Ihren Angabe=
n liefern, wie unten angeforderten so zu helfen, suchen Sie Ihre Datei einf=
ach und f=FCr die schnelle =DCbertragung von Ihrem Fonds zu Ihnen.

Vollst=E4ndiger Name: _______________________
Vollst=E4ndige Adresse: ____________________
Country of Residence: ____________
Nationalit=E4t: __________________
Beruf: ______________________
Alter: __________ Sex: _____________
Telefon-Nummer: ________________

Kontakt National Westminster Bank Plc f=FCr Anspr=FCche unter: {bargeldpost=
@gmail.com}.

Bitte geben Sie Ihre Datum der Auslosung Reference Number, Chargennummer un=
d gewinnende Nummer, kann diese auf der Oberseite dieser Nachricht gefunden=
 werden.

Au=DFerdem sollten Sie Ihre Telefonnummer geben, zum Auffinden der Datei le=
icht. Aus Sicherheitsgr=FCnden empfehlen wir Ihnen, diese Informationen ver=
traulich von der =D6ffentlichkeit, bis Ihr Anspruch bearbeitet und wurden S=
ie entlassen. Dies ist Teil unserer Sicherheitsprotokoll, um Doppelerfassun=
gen behaupten und ungerechtfertigte / unbefugte Personen nutzen dieses Prog=
ramm durch Nicht-Teilnehmer oder inoffizielle Mitarbeiter zu vermeiden.

Hinweis: alle Gewinne MUSS behauptete vor dem 28. M=E4rz 2013 sonst die Fon=
ds als beansprucht und schlie=DFlich f=FCr wohlt=E4tige Zwecke gespendet we=
rden zur=FCckgegeben werden.

Herzlichen Gl=FCckwunsch noch einmal auf Ihre Gewinnchancen!!

Mit freundlichen Gr=FC=DFen.
Mrs. Ashwaq Asimah.
Nahost-Gewinner Officer,
Cordinator,
USA Lottery 2013.

------=_NextPart_000_0001_1151435D.65F4A595
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<span style=3D"font-family: Arial, Helvetica, sans-serif; font-size: 10pt">=
<br />
<br />
<div>UNITED STATES OF AMERICA INT'L Lotterie INC<br />
100 W 33rd St, NEW YORK, NY, 10001-2900, USA<br />
CITY: NEW YORK,<br />
NY, 10001-2900,<br />
USA.<br />
<br />
Sehr geehrter Herr / Frau,<br />
<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HE=
RZLICHEN GL&Uuml;CKWUNSCH!<br />
<br />
Wir freuen uns, Ihnen Ihren Gewinn am 26. Februar 2013 aus den Vereinigten =
Staaten von America International Lottery Program, die teilweise auf einem =
elektronischen Auswahl der Gewinner mit ihrer E-Mail-Adressen basiert infor=
mieren.<br />
<br />
Ihre E-Mail-Adresse wurde an Ticket-Nummer beigef&uuml;gt; 359937283, Serie=
nnummer 4903784019 Diese Chargen ziehen die gl&uuml;cklichen Zahlen wie fol=
gt: 2-5-11-22-30 Zusatzzahl 26, die somit gewann die Lotterie in der zweite=
n Kategorie..<br />
<br />
Alle Teilnehmer wurden durch ein Computer Wahlgang System von Nine hundertt=
ausend E-Mail-Adressen aus Europa, dem Nahen Osten, Kanada, Australien, Asi=
en und Afrika als Teil unserer internationalen Promotions-Programm, das j&a=
uml;hrlich durchgef&uuml;hrt wird gezeichnet ausgew&auml;hlt.<br />
<br />
Diese Lotterie wurde gef&ouml;rdert und gesponsert von einem Konglomerat vo=
n einigen multinationalen Unternehmen als Teil ihrer sozialen Verantwortung=
 gegen&uuml;ber den B&uuml;rgerinnen und B&uuml;rgern in den Gemeinden, in =
denen sie operative Basis, und Sie werden mit einer Gewinnsumme von $ 1.000=
.000,00 USD berechtigt. (One Million US-Dollar nur)<br />
<br />
HOW TO Ihren Anspruch: Kontaktieren Sie einfach unseren arabischen und asia=
tischen Bank zahlen.<br />
<br />
National Westminster Bank Plc.<br />
Name: DR. JOHN Cunnane<br />
E-mail: bargeldpost@gmail.com<br />
<br />
Es wird empfohlen, Ihre Anspr&uuml;che Rechtsanwalt / Agenten mit Ihren Ang=
aben liefern, wie unten angeforderten so zu helfen, suchen Sie Ihre Datei e=
infach und f&uuml;r die schnelle &Uuml;bertragung von Ihrem Fonds zu Ihnen.=
<br />
<br />
Vollst&auml;ndiger Name: _______________________<br />
Vollst&auml;ndige Adresse: ____________________<br />
Country of Residence: ____________<br />
Nationalit&auml;t: __________________<br />
Beruf: ______________________<br />
Alter: __________ Sex: _____________<br />
Telefon-Nummer: ________________<br />
<br />
Kontakt National Westminster Bank Plc f&uuml;r Anspr&uuml;che unter: {barge=
ldpost@gmail.com}.<br />
<br />
Bitte geben Sie Ihre Datum der Auslosung Reference Number, Chargennummer un=
d gewinnende Nummer, kann diese auf der Oberseite dieser Nachricht gefunden=
 werden.<br />
<br />
Au&szlig;erdem sollten Sie Ihre Telefonnummer geben, zum Auffinden der Date=
i leicht. Aus Sicherheitsgr&uuml;nden empfehlen wir Ihnen, diese Informatio=
nen vertraulich von der &Ouml;ffentlichkeit, bis Ihr Anspruch bearbeitet un=
d wurden Sie entlassen. Dies ist Teil unserer Sicherheitsprotokoll, um Dopp=
elerfassungen behaupten und ungerechtfertigte / unbefugte Personen nutzen d=
ieses Programm durch Nicht-Teilnehmer oder inoffizielle Mitarbeiter zu verm=
eiden.<br />
<br />
Hinweis: alle Gewinne MUSS behauptete vor dem 28. M&auml;rz 2013 sonst die =
Fonds als beansprucht und schlie&szlig;lich f&uuml;r wohlt&auml;tige Zwecke=
 gespendet werden zur&uuml;ckgegeben werden.<br />
<br />
Herzlichen Gl&uuml;ckwunsch noch einmal auf Ihre Gewinnchancen!!<br />
<br />
Mit freundlichen Gr&uuml;&szlig;en.<br />
Mrs. Ashwaq Asimah.<br />
Nahost-Gewinner Officer,<br />
Cordinator,<br />
USA Lottery 2013.</div></span>

------=_NextPart_000_0001_1151435D.65F4A595--



From bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org  Wed Feb 27 17:57:25 2013
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE1321F8964 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Wed, 27 Feb 2013 17:57:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.769
X-Spam-Level: ****
X-Spam-Status: No, score=4.769 tagged_above=-999 required=5 tests=[BAYES_50=0.001, MISSING_SUBJECT=1.762, RCVD_IN_DNSWL_LOW=-1, TVD_SPACE_RATIO=2.219, URIBL_PH_SURBL=1.787]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G1GU97sbNKwx for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Wed, 27 Feb 2013 17:57:24 -0800 (PST)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id 1522021F877A for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Wed, 27 Feb 2013 17:57:21 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id 0E5F614A123; Thu, 28 Feb 2013 01:57:14 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 3053C14A121 for <ietf-ssh@netbsd.org>; Thu, 28 Feb 2013 01:57:13 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 3UY-GvhE-j8g for <ietf-ssh@netbsd.org>; Thu, 28 Feb 2013 01:57:12 +0000 (UTC)
Received: from smtp1.dc0.gpaas.net (smtp1.dc0.gpaas.net [217.70.185.10]) by mail.netbsd.org (Postfix) with ESMTP id 98B6414A11C for <ietf-ssh@netbsd.org>; Thu, 28 Feb 2013 01:57:11 +0000 (UTC)
Received: from mfilter22-d.gandi.net (mfilter22-d.gandi.net [217.70.178.150]) by smtp1.dc0.gpaas.net (Postfix) with ESMTP id 3853B5C59B for <ietf-ssh@netbsd.org>; Thu, 28 Feb 2013 01:39:04 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter22-d.gandi.net
Received: from smtp1.dc0.gpaas.net ([217.70.185.10]) by mfilter22-d.gandi.net (mfilter22-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 6QYAB-COhAb5 for <ietf-ssh@netbsd.org>; Thu, 28 Feb 2013 01:39:02 +0100 (CET)
X-Originating-IP: 172.17.18.34
Received: from customer.gpaas.net (unknown [172.17.18.34]) by smtp1.dc0.gpaas.net (Postfix) with SMTP id E3BCE5C593 for <ietf-ssh@netbsd.org>; Thu, 28 Feb 2013 01:39:01 +0100 (CET)
Received: by customer.gpaas.net (sSMTP sendmail emulation); Thu, 28 Feb 2013 01:39:01 +0100
Date: Thu, 28 Feb 2013 01:39:01 +0100
To: ietf-ssh@netbsd.org
Subject: 
X-PHP-Originating-Script: 5000:info_image.php
From: goronkov_matvei@email.ru
Content-type: text/plain; charset=windows-1251
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list
Message-Id: <20130228015714.0E5F614A123@mail.netbsd.org>

http://murl.kz/JvuQ8
