Jira (BOLT-290) Decompose --insecure flag
Title: Message Title Zach Reichert assigned an issue to Zach Reichert Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: Zach Reichert Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title Zach Reichert commented on BOLT-290 Re: Decompose --insecure flag Alex Dreyer Should `--[no-]host-key-check` just be ignored for SSH? Same question for --[no-]ssl with WINRM only WINRM nodes. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title Alex Dreyer commented on BOLT-290 Re: Decompose --insecure flag I think you have that backwards. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title Zach Reichert commented on BOLT-290 Re: Decompose --insecure flag You are correct, reverse that. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title
Glenn Sarti commented on BOLT-290
Re: Decompose --insecure flag
Instead of -
ssl I would suggest
https and
-http. This more accurately describes what is going on as it's changing the uri protocol. Also to be, pedantic what about TLS?
Admittedly the PowerShell command does use --UseSSL
SYNTAX
Enter-PSSession [[-ConnectionUri] ] [-AllowRedirection] [-Authentication {Default | Basic | Negotiate | NegotiateWithImplicitCredential | Credssp |
Digest | Kerberos}] [-CertificateThumbprint ] [-ConfigurationName ] [-Credential ] [-EnableNetworkAccess] [-SessionOption
] []
Enter-PSSession [-ComputerName] [-ApplicationName ] [-Authentication {Default | Basic | Negotiate | NegotiateWithImplicitCredential |
Credssp | Digest | Kerberos}] [-CertificateThumbprint ] [-ConfigurationName ] [-Credential ] [-EnableNetworkAccess] [-Port
] [-SessionOption ] [-UseSSL] []
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title Zach Reichert assigned an issue to Unassigned Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: Zach Reichert Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: David Kramer Fix Version/s: BOLT 0.15.1 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: David Kramer Fix Version/s: BOLT 0.15.1 Fix Version/s: BOLT 0.16.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: Alex Dreyer Release Notes Summary: * Breaking CLI Change *The --insecure and -k options are no longer available. They have been replaced with a [no-]ssl option for winrm and a [no-]check-host-keys option for the ssh transport. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Issue Type: Improvement Assignee: Unassigned Created: 2018/01/03 10:53 AM Priority: Normal Reporter: Alex Dreyer The --insecure flag has a different meaning for different transports and is not specific enough for future features. SSH: For ssh we should replace the --insecure flag with --no-host-key-check. In the config we should expose a host-key-check option that defaults to true. WINRM: for the winrm transport we should replace - insecure with --ssl/ -no-ssl on the commandline. In the config we should have a single ssl option that defaults to to true. Add Comment
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: David Kramer The --insecure flag has a different meaning for different transports and is not specific enough for future features.SSH:For ssh we should replace the --insecure flag with --no-host-key-check. In the config we should expose a host-key-check option that defaults to true.WINRM:for the winrm transport we should replace --insecure with --ssl / and --no-ssl on the commandline. In the config we should have a single ssl option that defaults to to true. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-290
Decompose --insecure flag
Change By:
Michael Smith
The --insecure flag has a different meaning for different transports and is not specific enough for future features.SSH:For ssh we should replace the {{\ - \ -insecure }} flag with {{\ - \ - \[ no \ - \] host-key-check }} . In the config we should expose a {{ host-key-check }} option that defaults to true.WINRM:for the winrm transport we should replace {{\ - \ -insecure }} with {{\ - \ - ssl and -- \[ no \ - \] ssl }} on the commandline. In the config we should have a single {{ ssl }} option that defaults to to true.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
