Skip to Content.
Sympa Menu

cat-users - Re: [cat-users] A different topic - invitations and leakage of tokens

cat-users AT lists.geant.org

Subject: The mailing list for users of the eduroam Configuration Assistant Tool (CAT)

List archive

Re: [cat-users] A different topic - invitations and leakage of tokens


Chronological Thread 
  • From: Stefan Winter <stefan.winter AT restena.lu>
  • To: A.L.M.Buxey AT lboro.ac.uk
  • Cc: "cat-users AT geant.net" <cat-users AT geant.net>
  • Subject: Re: [cat-users] A different topic - invitations and leakage of tokens
  • Date: Fri, 6 Nov 2015 09:53:04 +0100
  • List-archive: <https://mail.geant.net/mailman/private/cat-users/>
  • List-id: "The mailing list for users of the eduroam Configuration Assistant Tool \(CAT\)" <cat-users.geant.net>
  • Openpgp: id=AD3091F3AB24E05F4F722C03C0DE6A358A39DC66; url=http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66

Hi,

> 1) please do not use our direct emails....please can we have either our NRO
> service desk
> or our support group email address as the email for our federation
> (currently
> you pull the details from the eduroam DB - i guess this needs to be looked
> at)

Well, I can work with what I have. Right now, there is no notion of "the
role-based address that NROs use as helpdesk address" - the eduroam
Operations database contains an admin contact field, and that is what it
is; maybe an individual, maybe a role. (And in order to submit eduPKI
certificate requests, there is typically at least one personal mail in
the set).

I understand that direct personal names and mails are not appreciated
and have removed the Reply-To for the time being. That is, until I find
"somewhere" an authoritative source of mail addresses to use for such
communication.

> 2) put nice wrapped around the token ** THIS IS PRIVATE AND ONLY FOR YOU,
> DO NOT SHARE
> ON PUBLIC FORUMS * or somesuch ? :-)

I now have this in branch_1_1 and trunk:

"Do NOT forward the mail before the token has expired - or the
recipients may be able to consume the token on your behalf!"


I hope that makes it clear.

While inspecting that code, I also realised that the expiration
timestamp of the invitation is only sent in a subset of circumstances:
only if the invitation is from a fed admin *and* he invited an existing
IdP from the list of known IdPs.

The other two cases, invitation of a "new" IdP and co-invitation of one
inst admin to another, did not explicitly state the timestamp of expiration.

I have now fixed this for the next release; everybody gets their
expiration info unconditionally.

> 3) eduroamCAT users list is populated by users (and sites) of
> eduroamCAT...as well
> as NRO admins... might I suggest that we have a federation/NRO admin list
> aas well as users and
> dev. this sort of discussion would then go there :-)

Again, I have to work with what I have :-)

I can pull out all fed admin mails from the CAT DB and send to all of
course; or the next best option is to take this to eduroam Europe
coordination && GeGC. Which is maybe not so bad (considering that very
many countries world-wide make use of CAT, and I'll only hit a few which
don't care about the topic). Point taken :-)

Greetings,

Stefan Winter

--
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et
de la Recherche
2, avenue de l'Université
L-4365 Esch-sur-Alzette

Tel: +352 424409 1
Fax: +352 422473

PGP key updated to 4096 Bit RSA - I will encrypt all mails if the
recipient's key is known to me

http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66

Attachment: 0x8A39DC66.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature




Archive powered by MHonArc 2.6.19.

Top of Page