Skip to Content.
Sympa Menu

technical-discuss - RE: [InC-Technical] InCommon Baseline Expectations Metadata Requirements

Please Wait...

technical-discuss@incommon.org

Subject: InCommon Technical Discussions

List archive

RE: [InC-Technical] InCommon Baseline Expectations Metadata Requirements


Chronological Thread 
  • From: "Cantor, Scott" <cantor.2@osu.edu>
  • To: David Langenberg <davel@uchicago.edu>, Nick Roy <nroy@internet2.edu>, "technical-discuss@incommon.org" <technical-discuss@incommon.org>
  • Subject: RE: [InC-Technical] InCommon Baseline Expectations Metadata Requirements
  • Date: Thu, 9 Nov 2017 14:47:55 +0000
  • Accept-language: en-US
  • Authentication-results: spf=pass (sender IP is 128.146.138.11) smtp.mailfrom=osu.edu; incommon.org; dkim=none (message not signed) header.d=none;incommon.org; dmarc=pass action=none header.from=osu.edu;
  • Ironport-phdr: 9a23:XA8I7BFIFsj+bgqPxOXuf51GYnF86YWxBRYc798ds5kLTJ76p869bnLW6fgltlLVR4KTs6sC0LuG9fi4EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQtFiT6+bL9oMBm6sRjau9ULj4dlNqs/0AbCrGFSe+RRy2NoJFaTkAj568yt4pNt8Dletuw4+cJYXqr0Y6o3TbpDDDQ7KG81/9HktQPCTQSU+HQRVHgdnwdSDAjE6BH6WYrxsjf/u+Fg1iSWIdH6QLYpUjm58axlVAHnhzsGNz4h8WHYlMpwjL5AoBm8oxBz2pPYbJ2JOPZ7eK7WYNEUSndbXstJVyJPHJ6yb5cBAeQCM+ZXrYj9qEcBohalCgmgGOfixydUinPq36A31fkqHwHc3AwnGtIDqHrYocvvO6cUTeC1y7PIwS3eZP1LxTj975TIcgwvrfqRWr9/bdDeyU8zFwPClFWcs5LpMiiS1uQWrmiX9fRvWv+yi2M+rQx6vzuhxt80h4XUmo4YxUrI+Cp7zYovKtC0VFR3bcO6HJZUry2WKop7T8w4T211pCo3yKcKtYC0cSUI0pgr2h/SZvKff4iG/B3uV/qdLDJ9iX9rfL+yhgq+/E29xeLhVcS50VNHoTFfndXSs30CzQHc5taGR/Z740yvwyyA1xrJ5eFBOU00lbTUK5omwrMojpQerUPNEjP4lUnvkqKYb1go9vGv6+v8fLrqvJicN5Joig7lNaQuh8q/DvkiPggWRWib/vi826P/8k3lQbVKifs2nrPesJDHOcQboqm5AwhW0oo59xm/CDKm3MwZnXkBMl1FZAqKg5X1N1zBOvz1AvWyj06jnTt33fzKI6PtD5HVInjGirjhfLJ960BGyAo0yNBS/45bBasHIPLvXU/xrsbUAgEiPgyz2ObnFc9x2Z0DVmKSGqOZKr/dsUeU5uIzJOmBfI4VuDDhJPgi4v7uiHg5mVkHcamux5sXZ2m0Huh4LEqFYXrshNYBHnsQsQo6VeDllVyCUSVPaHavRKI8/So2CIanDYfYWoCtm6KN0D26Hp1QemBJFEqMEXH2eIWYRfsAcjydLdJ8km9Mab/0Z4Y/1B3mkAb8xLdhJOfO9WVMuZv92dxd+ubTlBo7+jsyAsiAhSXFaWB/nSsyQC5+iKZlpl1Vy1Gf3LJ+juACU9Ff+qUNGk0mOJXcye1xAtS3VgPadcqSU36nRN6hBDQ2SJQ22dBEKxJhFt6iiBHI1i7vD74OnKGQH7Q19Knb2n32IYB60XmQh4c7iFxzCOBGM3GhnOo3zAPUG5KD2xGSnqC2cr5ahgbK73rFwGaT6hILGDVsWLnICChMLnDdqs70swabF+ej
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

> So, maybe I missed something here (I have a cold today), but why do we care
> about the foreign site’s SSL grade? Having SSL, yes, I can see that, but
> beyond that, if my institution wants to run SSLv1 with a 256K key signed by
> CNNIC, isn’t that a risk that only affects us?

Who is "us"? The IdP? Clearly your security affects me as an SP if I depend
on your logins. If you're the SP, then I certainly care if I'm releasing data
to you whether the site is actually doing weak TLS, particularly when
encryption isn't used (and I don't think eduGAIN as a whole requires SPs have
keys, does it?)

Mostly it's a barometer of incompetence.

Whether I would actually do something with this data if I had it, I don't
know. In terms of my default release policy, I think I'd strongly consider
it. Contract services have explicit release rules, but for ad hoc federation,
yeah, I think I'd tell you to fix your site if you want our data.

Is this the highest priority for InCommon? No, but we're just talking here.

-- Scott

Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.19.

Top of Page