Skip to content

ssh steps dependency on ssh-forever #5

@jedi4ever

Description

@jedi4ever

Hi, I've had a go with cuken again. The current gem (not github) fails to setup some of the ssh-steps.
It for example

  1. complains about the "-b" option at the end of the ssh-forever call
  2. ssh-forever sets up a lot of keys etc. on the box (you don't want to change your target system in any way)
  3. is spawns shells
  4. is changes the .ssh/config files (I would not want that)

I'd love to use cuken for #veewee, but currently I'm still undecided given the ssh-forever dependency.

I see the value of running it just through the command cmd/cuken sweet,
but I think there room for the same implementation through net/ssh .

How would you feel about this? Do I make a new cuken/netssh include and create the same ssh steps?
Or I create a step called And I successfully sshrun or something similar.

thanks for feedback

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions