I am really new at this so please dont laugh to hard.
Looking at the cookbook example 5.3 it would appear that we could send a file from our mainframe to a remote server, using it to encrypt the file with PGP or GPG on that server and then receive the file back seamlessly.
Is this what I am seeing and if this is the case is there a point when the file reaches the remote server that the file contents are "exposed" or "open".
cookbook examples
Re: cookbook examples
Example 5.3 is here: http://dovetail.com/docs/coz/cookbook.html#4_3
This example demonstrates using the Co:Z Launcher running on z/OS to remotely run a script on a target server that uses tools like PGP.
This is an alternative to using Co:Z SFTP, which is simply a SSH/SFTP client and server for z/OS.
(So, really, this post is is the wrong forum )
The Co:Z Launcher implements what we call "hybrid batch" -
Here is a brief video introduction: http://www.youtube.com/embed/WlZbN_vs7us
What might be a little confusing is that you can use hybrid batch (via the Co:Z launcher) to use an "appliance server" as a gateway for transforming and sending files to other servers. Here is an article in z/Journal that describes this technique:
http://enterprisesystemsmedia.com/artic ... ge-gateway
To answer your question about example 5.3 -
Assuming that you have encryption enabled (ssh-tunnel=yes) for the Co:Z Launcher, the data is only "in the clear" at the following points:
- as it is copied over a local socket (the loopback adapter, not over the network) between the sshd process and the fromdsn process
- as it is copied (in memory) from the fromdsn pipe into the gpg command.
It is never in the clear over the network or on disk. The hybrid batch video intro might help to clarify this.
This example demonstrates using the Co:Z Launcher running on z/OS to remotely run a script on a target server that uses tools like PGP.
This is an alternative to using Co:Z SFTP, which is simply a SSH/SFTP client and server for z/OS.
(So, really, this post is is the wrong forum )
The Co:Z Launcher implements what we call "hybrid batch" -
Here is a brief video introduction: http://www.youtube.com/embed/WlZbN_vs7us
What might be a little confusing is that you can use hybrid batch (via the Co:Z launcher) to use an "appliance server" as a gateway for transforming and sending files to other servers. Here is an article in z/Journal that describes this technique:
http://enterprisesystemsmedia.com/artic ... ge-gateway
To answer your question about example 5.3 -
Assuming that you have encryption enabled (ssh-tunnel=yes) for the Co:Z Launcher, the data is only "in the clear" at the following points:
- as it is copied over a local socket (the loopback adapter, not over the network) between the sshd process and the fromdsn process
- as it is copied (in memory) from the fromdsn pipe into the gpg command.
It is never in the clear over the network or on disk. The hybrid batch video intro might help to clarify this.
-
jack.weatherford
- Posts: 21
- Joined: Mon Aug 05, 2013 9:50 am
Re: cookbook examples
sorry for mis posting but thanks for the reply.
You answered my question. Next time I will attempt to get it directed to the proper forum.
You answered my question. Next time I will attempt to get it directed to the proper forum.
Re: cookbook examples
No worries, Jack... its a very common mistake and not really an issue.
I was really hoping to distinguish between Co:Z SFTP and Co:Z (Launcher/Dataset Pipes), which is confusing to a lot of folks.
Regards,
Kirk
I was really hoping to distinguish between Co:Z SFTP and Co:Z (Launcher/Dataset Pipes), which is confusing to a lot of folks.
Regards,
Kirk