Skip to Content.
Sympa Menu

comanage-dev - Re: [comanage-dev] SSH/Domestication

Subject: COmanage Developers List

List archive

Re: [comanage-dev] SSH/Domestication


Chronological Thread 
  • From: "Michael R. Gettes" <>
  • To: " List" <>
  • Subject: Re: [comanage-dev] SSH/Domestication
  • Date: Thu, 19 Aug 2010 16:29:38 -0400
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=jJGTDAZW9dMdaFHzmuGJzfQWIzXJRIDYS1Fto6MaBdVwMvt91pHGDyTZmfKLQaEWRY Ok3yazJxHqEqW2D/bKVlZJNSubgRz+9FDIzA8mJMNkt6NSEKP2PAD9GVOYEaxW+aK+Wi H4X98/dbIIWBa42MkyTiVrcJUG4CaBD5vi3q0=

This might be heresy to suggest... what about a web-based SSH?
Does this make the problem more tractable?

/mrg

On Aug 19, 2010, at 16:08, Benn Oshrin wrote:

> As an exercise, following a call with Scott Koranda, I took a stab at
> adding “SSH” to the registry of domesticated applications.
>
> https://spaces.internet2.edu/display/COmanage/Registry+of+Domesticated+Applications
>
> Unsurprisingly, I ran into a couple of problems.
>
> First, what exactly do we mean by “SSH”? The registry is for applications,
> not protocols. There are a number of applications that support SSH, both
> clients and servers. Arbitrarily, I selected OpenSSH.
>
> Secondly, OpenSSH is actually pretty domesticated. It integrates with the
> underlying environment for authentication, authorization, groups, etc.
> When we say SSH, I think we're actually talking about federated
> provisioning, which in some ways isn't really an SSH problem.
>
> Thoughts? First on what the actual problem definition is here, and second
> on how we want to capture it (ie: Registry or not).
>
> Thanks,
>
> -Benn-




Archive powered by MHonArc 2.6.16.

Top of Page