Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
German Umlaute within description of a share are displayed as '?'. Umlaute within directory- or filenames are displayed correct.
IE 7, FF 2
Logged In: YES
Seems like the machine is sending the German Umlaute as "3F" which is the "?" symbol.
I've mailed the author of the jCIFS library for this, maybe there is a flag missing to force the comments in unicode (Windows servers seem to send the comments automatically in unicode).
004E0: 6B 65 6E 00 00 46 61 6B 75 6C 74 3F 74 20 66 3F |ken..Fakult?t f?|
Logged In: NO
the problem seems be the jCIFS library sending RPC-calls to the NetApp machine.
The exception causes a switch to the old (non-rpc) LanManager netShareEnum-functions which only transfer ascii characters in share comments.
I added a new version of the jCIFS library (1.2.15k, not yet final) to the new release (0.44). The new jCIFS library has also support for resolving SIDs in ACLs (so no more need for LDAP).
My first tests with the gfiler looked very good. So maybe you can give a try to the new release and check if the other things are also ok ?
by using the RPC functions, comments in shares should now display unicode characters properly.
Logged In: YES
I tested the changes so far.
Anythings works fine now.
- RPC-SID resolve
- Unicode Char
- Zip Download
I haven't testet the ldap client implemenation, because there is no need for us.
New Feature of 'dirinfo.txt' is nice to have.
Thanks so far
Is there any plan forn implementing DACL change, not only display?
changing ACLs needs a lot of things:
list users / groups, list group members, change the ACLs
"list group members" is implemented in the jCIFS library, but not working with the filer.
"list users / groups" would need to be implemented as RPC or LDAP functions with some searching functionality.
Changing the ACLs also needs to be implemented in jCIFS. It may be possible to use a Samba tool called smbcacls instead, but I don't know how good that works.
Also I doubt that normal users will be able to use it without reading the specs for ACLs.