On Friday, 17 March 2017 17:28:12 UTC+1, [email protected]  wrote:
> On Friday, March 17, 2017 at 5:37:38 AM UTC-4, Gervase Markham wrote:
> > On 16/03/17 17:20, douglas beattie wrote:
> > > Yes, RAs (trusted role employees) need to have the technical ability
> > > to manually add domains to accounts.  They can verify domains in one
> > > of the 10 different methods and some of those involve manually
> > > looking in who-is for registrant info, using a DAD or in calling the
> > > contact.  When one of these is used, we collect the vetting data then
> > > the RA can add/approve that domain.
> > 
> > But is the addition of the domain gated on the
> > uploading/attachment/submission of what could plausibly be vetting data?
> 
> It's gated on the RA following the correct process which is uploading the 
> documents in one system and then approving the domain in a different system.
> 
> > I mean, I understand you can't programmatically check that a person has
> > made a phone call. But you can require them to write a report of the
> > results of that phone call and not allow addition of the domain until
> > they've done it. Yes, they could just put "flibbertigibbet" into the
> > text box, but that at least shows they are deliberately bypassing the
> > process.
> > 
> > If the addition is so gated, what did the employee in this case do? Did
> > they upload bogus data?
> 
> No bogus data was uploaded.
> 
> Doug

The suspense is killing... What "non bogus" data was uploaded then? Can't have 
been any "plausible vetting data" can it?

CU Hans
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy
            • Re: ... Gervase Markham via dev-security-policy
            • Re: ... douglas.beattie--- via dev-security-policy
            • Re: ... Gervase Markham via dev-security-policy
            • Re: ... Gervase Markham via dev-security-policy
            • Re: ... douglas.beattie--- via dev-security-policy
            • Re: ... Gervase Markham via dev-security-policy
            • Re: ... douglas.beattie--- via dev-security-policy
            • Re: ... Nick Lamb via dev-security-policy
            • Re: ... Gervase Markham via dev-security-policy
            • Re: ... douglas.beattie--- via dev-security-policy
            • Re: ... okaphone.elektronika--- via dev-security-policy
            • Re: ... tarah--- via dev-security-policy
            • Re: ... Gervase Markham via dev-security-policy
            • Re: ... Nick Lamb via dev-security-policy
  • RE: Suspicious test.com Ce... Nio via dev-security-policy
  • RE: Suspicious test.com Ce... Nio via dev-security-policy

Reply via email to