@salass00

Quote:

Some of the latin character encodings support umlauts; e.g., ISO-8859-1.

I knew that displaying UTF-8 was hard, but I didn't realize that it also prevents accessing files with "non-standard" characters. I thought that you'd still be able to read the files.

Hans

@Hans

Quote:

Yeah but conversion is complex, because of the lack of 1 to 1 correspondance between uf8 and 8bit encodings, and / or potentialy missing characters.

Quote:

I'm pretty sure you can actually. DOS doesn't care about encoding as far as I understand it.

I just created a file name schön (o with umlaut incase that doesn't get encoded properly between here and the website ) on my linux box, coppied it by ftp to ram: with pftp and could open it fine.

The filename displayed as

's' 'c' 'h' 'captial A tilda' 'paragraph mark' 'n'

but was still accessable from the workbench, or the shell if I used name completion. I might have a challenge trying to type it though.

The bigger problem would happen if I create a file called schön on the amiga side and try and send that. That ends up as sch?n (invaid encoding) in the filemanager, and again I can access it with name completeion, but this time I really can't type it at all.

@broadblues

Can you also open such files with ASL requesters?

I'm guessing that saving might be an issue if ASL requesters also do character set conversion.

Hans

@broadblues

Yes i tried that aswell and the üproblem is not FTP (in any derivate i tried).
That works pretty well.
The problem is inside (or missing from) smbfs/samba.
Accessing a share there will not let you use it once you copied, renamed or created it with such a character.

So i guess i might be in luck, at least when the new filesystem does the same as FTP does, otherwise i'm stomped again.

@Hans

Not tried with a FTP FS, but smbfs/samba will list the file, but access them.
Big problem, as my shares are virtually unusable.

@Hans

Quote:

I'm pretty sure it doesn't. The problem is that most components just assume that all file names and such are in the "correct" codeset and do no conversion or checking whatsoever.

This only "works" as long as you only use native filesystems like FFS, SFS, JXFS, NGFS and so on that also make this assumption and never exchange disks with someone who uses a different codeset.

Other OSes have moved on to using utf-8 only and ideally AmigaOS should too.

@broadblues

Quote:

I just realised an additional problem: in UTF-8 there is more than one way of expressing an accented character. There are conventions for normalisation that should prevent this from being a problem... but you never know...

@salass00
I'll be VERY interested to try this with my FolderSync2, when it's a bit more mature, as FTP Mount is unreliable these days & SMBFS doesn't work at all (it nearly works but that's not enough for my heavy usage).

edit: I see discussion of UTF-8/etc support. FolderSync2 has a UTF-8 parsing mode, which works well with 'dumb' FTP Mount passing UTF-8 sequences straight through (from a Windows PC).

The reason I can't use SMBFS is it's UTF-8 support is broken/incomplete AND it has no "UTF-8 pass through" mode. (If I had time I'd investigate adding this myself. It would presumably be trivial, if you could get it to compile in the first place...)

So please ensure your SFTP filingsystem has the option for a dumb "UTF-8 pass-through" mode.

I just wrote a README file with some usage instructions for the ssh2-handler.

All of the relevant FUSE operations are implemented and working, with the exception of symlink() used for creating soft links. For some reason the libssh2_sftp_symlink() call just returns an error and won't do anything for me.

Some UNIX programs which depend on st_ino/ObjectID to see if files are the same or different failed when used with ssh2-handler because I was leaving this field set to zero.

I've now changed the code to generate a hash from the file system path instead.

@salass00


Please keep the updates coming

What happened with this project? Was it released?

@salass00

Hi, I tried your last beta (v53.5) on an up to date beta
system and my shell account and had pretty mixed results.

It connected, but was exceptionally slow and seemed to lock
up all other disk access during any SSH disk activity.

Any chance you'll be releasing any more beta's for AmigaOS
(vs MattyOS)?

Thanks,

PJS

@pjs
Where is it possible to download (beta) SFTP from?

@ChrisH

I think you'll ned beta components of amigaOS 4.1 (not yet released).

@ChrisH

I think you'll need beta components of amigaOS 4.1 (not yet released).

@K-L
That doesn't answer my question :)

@ChrisH

True indeed

I don't know if beta tests are already open for OS4.1 beta testers but maybe this will be sorted via PM (since we, simple users, are still with older components)

@ChrisH

As K-L mentioned, i'm pretty sure beta testing is closed to some users.
I have never seen a link as to where it could be downloaded.

But it would be really nice to get some updates on the development (wink, wink)

Since yesterday was a bit cooler I spent some time and implemented ssh-agent support in ssh2-handler.

Another feature I've added is an option to set the root dir of the mounted volume.

These will both be available in the next release (V53.7).

@ChrisH

Ssh2-handler is available (along with the required updated filesysbox.library) to AmigaOS and Enhancer Software beta testers.

@salass00

Do i understand it correctly that SFTP can provide an SSH connection from the outside, if needed?