We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
We have a cron job that produces an xml file and uses sftp to push it to
the VMS system. In the script it did a "cd pipeline_data" which was a
system logical for where the file needs to go. This doesn't work as SSL doesn't appear to understand logicals. I had to change it to "cd /lda105/pipeline_data" to get it to work.
This breaks my rule that no script/com file should have a real device
name except for sys$manager:logicals.com. I put a remark in the
logicals.com to remind me of the new dependency if that logical changes.
On 2024-08-20, jeffrey_dsi <jeffrey@digitalsynergyinc.com> wrote:
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
We have a cron job that produces an xml file and uses sftp to push it to
the VMS system. In the script it did a "cd pipeline_data" which was a
system logical for where the file needs to go. This doesn't work as SSL
doesn't appear to understand logicals. I had to change it to "cd
/lda105/pipeline_data" to get it to work.
This breaks my rule that no script/com file should have a real device
name except for sys$manager:logicals.com. I put a remark in the
logicals.com to remind me of the new dependency if that logical changes.
Can you create a command procedure that looks up the logical and
writes out a temporary sftp command procedure containing the hardcoded current definition ?
That way, there's no permanent file containing the hardcoded definition.
On 2024-08-20, Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
On 2024-08-20, jeffrey_dsi <jeffrey@digitalsynergyinc.com> wrote:
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
We have a cron job that produces an xml file and uses sftp to push it to >>> the VMS system. In the script it did a "cd pipeline_data" which was a
system logical for where the file needs to go. This doesn't work as SSL
doesn't appear to understand logicals. I had to change it to "cd
/lda105/pipeline_data" to get it to work.
This breaks my rule that no script/com file should have a real device
name except for sys$manager:logicals.com. I put a remark in the
logicals.com to remind me of the new dependency if that logical changes. >>>
Can you create a command procedure that looks up the logical and
writes out a temporary sftp command procedure containing the hardcoded
current definition ?
That way, there's no permanent file containing the hardcoded definition.
Oops, sorry, ignore that. I missed the bit where you were pushing it
_onto_ the VMS system.
However, have you tried playing with the cd parameter to try and
force a lookup (for example by trying a leading "/" or something
that looks VMS-like such as "cd PIPELINE_DATA:" ?
Simon.
On 8/20/24 11:04, Simon Clubley wrote:
On 2024-08-20, Simon Clubleycd PIPELINE_DATA: fails the same as without the colon. I started an
<clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
On 2024-08-20, jeffrey_dsi <jeffrey@digitalsynergyinc.com> wrote:
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
We have a cron job that produces an xml file and uses sftp to push
it to
the VMS system. In the script it did a "cd pipeline_data" which was a
system logical for where the file needs to go. This doesn't work as SSL >>>> doesn't appear to understand logicals. I had to change it to "cd
/lda105/pipeline_data" to get it to work.
This breaks my rule that no script/com file should have a real device
name except for sys$manager:logicals.com. I put a remark in the
logicals.com to remind me of the new dependency if that logical
changes.
Can you create a command procedure that looks up the logical and
writes out a temporary sftp command procedure containing the hardcoded
current definition ?
That way, there's no permanent file containing the hardcoded definition. >>>
Oops, sorry, ignore that. I missed the bit where you were pushing it
_onto_ the VMS system.
However, have you tried playing with the cd parameter to try and
force a lookup (for example by trying a leading "/" or something
that looks VMS-like such as "cd PIPELINE_DATA:" ?
Simon.
issue with VSI so we'll see what they say.
On 8/20/24 3:30 PM, jeffrey_dsi wrote:
On 2024-08-20, jeffrey_dsi <jeffrey@digitalsynergyinc.com> wrote:
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
cd PIPELINE_DATA: fails the same as without the colon. I started an
issue with VSI so we'll see what they say.
Why do you think sftp has anything to do with SSL3? sftp runs over SSH,
not TLS.
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
On Tue, 20 Aug 2024 10:43:31 -0700, jeffrey_dsi wrote:
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
All versions of SSL that are called “SSL” are obsolete. All the versions recommended for use have “TLS” in their name: TLS 1.3 is the current one, I think some are still using TLS 1.2. Nothing older than that is worth
using any more.
On 8/20/2024 9:14 PM, Lawrence D'Oliveiro wrote:
On Tue, 20 Aug 2024 10:43:31 -0700, jeffrey_dsi wrote:
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
All versions of SSL that are called “SSL” are obsolete. All the
versions recommended for use have “TLS” in their name: TLS 1.3 is the
current one, I think some are still using TLS 1.2. Nothing older than
that is worth using any more.
Protocols that are named SSL are obsolete.
Software that are named SSL (and implementing TLS) is not obsolete.
On Tue, 20 Aug 2024 21:24:07 -0400, Arne Vajhøj wrote:
On 8/20/2024 9:14 PM, Lawrence D'Oliveiro wrote:
On Tue, 20 Aug 2024 10:43:31 -0700, jeffrey_dsi wrote:
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
All versions of SSL that are called “SSL” are obsolete. All the
versions recommended for use have “TLS” in their name: TLS 1.3 is the >>> current one, I think some are still using TLS 1.2. Nothing older than
that is worth using any more.
Protocols that are named SSL are obsolete.
Software that are named SSL (and implementing TLS) is not obsolete.
SSL v3 is obsolete.
On Tue, 20 Aug 2024 21:42:35 -0400, Arne Vajhøj wrote:
SSL V3 protocol is obsolete.
VMS SSL3 kit which is a port of OpenSSL 3.x is not obsolete.
Protocol <> Software
Ah. That wasn’t clear to me.
SSL V3 protocol is obsolete.
VMS SSL3 kit which is a port of OpenSSL 3.x is not obsolete.
Protocol <> Software
On 8/20/2024 5:22 PM, Craig A. Berry wrote:
On 8/20/24 3:30 PM, jeffrey_dsi wrote:
On 2024-08-20, jeffrey_dsi <jeffrey@digitalsynergyinc.com> wrote:
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13 >>>>>> after many conversations with VSI as to which version of SSL to run.
cd PIPELINE_DATA: fails the same as without the colon. I started an
issue with VSI so we'll see what they say.
Why do you think sftp has anything to do with SSL3? sftp runs over SSH,
not TLS.
SFTP is not using OpenSSH for TLS - FTP over TLS is FTPS.
But SFTP could use OpenSSL as basic cryptographic library
(AES, RSA etc.).
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
We have a cron job that produces an xml file and uses sftp to push it to
the VMS system. In the script it did a "cd pipeline_data" which was a
system logical for where the file needs to go. This doesn't work as SSL doesn't appear to understand logicals. I had to change it to "cd /lda105/pipeline_data" to get it to work.
This breaks my rule that no script/com file should have a real device
name except for sys$manager:logicals.com. I put a remark in the
logicals.com to remind me of the new dependency if that logical changes.
Jeff Coffield
www.digitalsynergyinc.com
We recently updated a customer to OpenVMS V8.4-2l3 and SSL3 v3.0-13
after many conversations with VSI as to which version of SSL to run.
We have a cron job that produces an xml file and uses sftp to push it
to the VMS system. In the script it did a "cd pipeline_data" which was
a system logical for where the file needs to go. This doesn't work as
SSL doesn't appear to understand logicals. I had to change it to "cd /lda105/pipeline_data" to get it to work.
This breaks my rule that no script/com file should have a real device
name except for sys$manager:logicals.com. I put a remark in the
logicals.com to remind me of the new dependency if that logical changes.
It turns out that the error was in OpenSSH that was also upgraded at the
same time as the switch to SSL3. VSI says the bug is fixed in OpenSSH V8.9-2i01 along with a lot of other fixes. I am going to start testing
that version next week.
On 2024-08-24, jeffrey_dsi <jeffrey@digitalsynergyinc.com> wrote:
It turns out that the error was in OpenSSH that was also upgraded at the
same time as the switch to SSL3. VSI says the bug is fixed in OpenSSH
V8.9-2i01 along with a lot of other fixes. I am going to start testing
that version next week.
Just curious: Did you try the "cd /pipeline_data" I suggested ?
Simon.
I did try that and it didn't work.
Jeff
On 8/27/24 05:37, Simon Clubley wrote:
On 2024-08-24, jeffrey_dsi <jeffrey@digitalsynergyinc.com> wrote:
It turns out that the error was in OpenSSH that was also upgraded at the >>> same time as the switch to SSL3. VSI says the bug is fixed in OpenSSH
V8.9-2i01 along with a lot of other fixes. I am going to start testing
that version next week.
Just curious: Did you try the "cd /pipeline_data" I suggested ?
Simon.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 437 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 194:18:53 |
| Calls: | 9,135 |
| Calls today: | 2 |
| Files: | 13,432 |
| Messages: | 6,035,425 |