cozsftp_server_config

Discussion of Co:Z sftp, a port of OpenSSH sftp for z/OS
Post Reply
Shady
Posts: 37
Joined: Wed Feb 24, 2010 10:50 pm

cozsftp_server_config

Post by Shady »

It's me again...


I used the cozsftp_server_config "fixed:" area to set up some options.

The Co:Z SFTP Guide says:
1. The fixed: section of /etc/ssh/cozsftp_server_config (highest priority and non-modifiable)
...
But I can change the settings after a connection is established.
This is a bit confusing me... I thought (because of "highest priority and non-modifiable") that this can't be modified after a connection is established.
That's not correct, isn't it? You just mean this won't be overridden by for example SFTP_ZOS_OPTIONS. Or is it a bug...?
Is it possible to don't let the user change a setting after the connection is established, for example for COZ_LOG?


/edit:
I recognized something at the moment:
with ls /+mode=... works. I can't override it (assumed I don't also set mode=.. in an other way, this will override the fixed section...?)
But ls /+loglevel=... --> I can override it...
I'm doing some wrong? I don't know...
coz
Posts: 392
Joined: Fri Jul 30, 2004 5:29 pm

Post by coz »

This works for me. Can you post:

1.) The contents of your cozsftp_server_config file
2.) The specific commands you are issuing
3.) The contents of your /+error.log file

We'll take a look to see if we can figure out what's going on.
Shady
Posts: 37
Joined: Wed Feb 24, 2010 10:50 pm

Post by Shady »

OK... I think it was my fault...
I was setting logging with COZ_LOG. It's logical that this dosen't work.


The other thing is...
When I specify

fixed:
mode=text
and in the sftp-server.rc:
SFTP_ZOS_OPT="mode=binary"

Then the binary option is active and I can override this.
I know that dosen't make sense but I was wondering until I found the error. It's correct that the lower option is active...?

Just a question...
It's fine when I don't specify the same option in an other search step...
coz
Posts: 392
Joined: Fri Jul 30, 2004 5:29 pm

Post by coz »

Glad you got the logging issue figured out. You *have* identified a bug with the way we process the options environment variable however. We'll fix this in the next release.
Post Reply