pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Victor Wagner <vitus@wagner.pp.ru>
To: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Subject: Re: Password identifiers, protocol aging and SCRAM protocol
Date: Wed, 9 Nov 2016 09:59:27 +0300
Message-ID: <20161109095927.701c32e8@fafnir.local.vm> (raw)
In-Reply-To: <CAB7nPqTGk+F2dw8=Gv8wXfm6eVHr=n9aAiMi_xtO7Or4r0AD+g@mail.gmail.com>
References: <CAB7nPqSL_V+0nD5i-XH_x1o5HTt2bT53vVwPUTHz8YT0hYRoPg@mail.gmail.com>
	<f606bf4d-6791-1b3a-a7e9-b676544b7f75@pgmasters.net>
	<CAB7nPqRhhJGhEeQn8omtS0x2s5YyjEuAtV1vdPt-7WVuC6OpcA@mail.gmail.com>
	<79774ac1-df34-6b20-1659-c020c3842ce1@iki.fi>
	<f28a48ef-cc89-3de6-131e-3d32e7267d4c@iki.fi>
	<CAB7nPqTxyM+3YbQuevYVZ9MzCBYFAyzSqH2Pk5BaRBy-4GdjfQ@mail.gmail.com>
	<CAB7nPqS6Pfz5+3CieROcXRUDRN41bZ274JfGiTMfhZtKku2HDg@mail.gmail.com>
	<CAB7nPqRy3krN8quR9XujMVVHYtXJ0_60nqgVc6oUk8ygyVkZsA@mail.gmail.com>
	<4f3a9e71-cb1b-ca44-a780-36d503671e45@iki.fi>
	<CAB7nPqRW5JvH8jj+zNjBL72EYDyj3qPdNGYWvuHNq9-BR63R_w@mail.gmail.com>
	<d60f8ddb-3ba5-2402-8951-7ae23ba0974b@iki.fi>
	<CAB7nPqQpek5pUUinmZNMr+n9+vgaUqaxZJ9zWRoMKM8e1uHRHw@mail.gmail.com>
	<CAB7nPqTxH8Nnvo0ii4w6881cT3OODgJcE7RFk-WaS+mYD-7pyg@mail.gmail.com>
	<20161109091309.6437a8b3@fafnir.local.vm>
	<CAB7nPqTGk+F2dw8=Gv8wXfm6eVHr=n9aAiMi_xtO7Or4r0AD+g@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On Wed, 9 Nov 2016 15:23:11 +0900
Michael Paquier <michael.paquier@gmail.com> wrote:


> 
> (This is about patch 0007, not 0001)
> Thanks, you are right. That's not good as-is. So this basically means
> that the characters here should be from 32 to 127 included.

Really, most important is to exclude comma from the list of allowed
characters. And this prevents us from using a range.

I'd do something like:

char prinables="0123456789ABCDE...xyz!@#*&+";
unsigned int r;

for (i=0;i<SCRAM_NONCE_SIZE;i++) {
     pg_strong_random(&r,sizeof(unsigned int))
     nonce[i]=printables[r%(sizeof(prinables)-1)]
     /* -1 is here to exclude terminating zero byte*/
}
    

> generate_nonce needs just to be made smarter in the way it selects the
> character bytes.



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (149+ messages)  latest in thread

Message-ID: <20161109095927.701c32e8@fafnir.local.vm>
Permalink:  ../20161109095927.701c32e8@fafnir.local.vm/
Also on:    postgresql.org/message-id/20161109095927.701c32e8@fafnir.local.vm

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: vitus@wagner.pp.ru
  Subject: Re: Password identifiers, protocol aging and SCRAM protocol
  In-Reply-To: <20161109095927.701c32e8@fafnir.local.vm>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox