jetwhiz / encfs4win

Windows port of EncFS
https://encfs.win
Other
402 stars 41 forks source link

Do Not support mount folder with name of double-byte languages. #55

Open gzl6 opened 8 years ago

gzl6 commented 8 years ago

Environment

As subjected. Error message "error saving configuration file".

Expected behavior vs. actual behavior

Folder with name or path of english language can be mounted

Steps to reproduce problem

  1. Relevant logs

Attach any relevant log files that can help to debug your issue (be sure to use the -v option for verbose logs).

jetwhiz commented 8 years ago

Hi @gzl6, thank you for the report!

When you say double-byte languages, are you referring to Big5 and the like, or UTF-8?

gzl6 commented 8 years ago

Yes, Big5 someting alike.

Date: Wed, 10 Aug 2016 09:07:55 -0700 From: notifications@github.com To: encfs4win@noreply.github.com CC: to_liwei@hotmail.com; mention@noreply.github.com Subject: Re: [jetwhiz/encfs4win] Do Not support mount folder with name of double-byte languages. (#55)

Hi @gzl6, thank you for the report!

When you say double-byte languages, are you referring to Big5 and the like, or UTF-8?

― You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

jetwhiz commented 8 years ago

Is this error only happening with encfsw.exe?

Have you tried using the command line program (encfs.exe) directly to see if the problem exists there as well?

gzl6 commented 8 years ago

1# Folder path with ASCII is ok to proceed

C:\Program Files (x86)\encfs>encfs d:\test x:\

Creating new encrypted volume.

Please choose from one of the following options:

enter "x" for expert configuration mode,

enter "p" for pre-configured paranoia mode,

anything else, or an empty line will select standard mode.

?>

2# If Folder path with double-byte languages, command window would be idle and has to use ctrl-c to quit.

From: JetWhiz [mailto:notifications@github.com] Sent: Sunday, August 14, 2016 2:22 AM To: jetwhiz/encfs4win encfs4win@noreply.github.com Cc: gzl6 to_liwei@hotmail.com; Mention mention@noreply.github.com Subject: Re: [jetwhiz/encfs4win] Do Not support mount folder with name of double-byte languages. (#55)

Is this error only happening with encfsw.exe?

Have you tried using the command line program (encfs.exe) directly to see if the problem exists there as well?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jetwhiz/encfs4win/issues/55#issuecomment-239634496 , or mute the thread https://github.com/notifications/unsubscribe-auth/AT-BctpsmeHKNrAzhRJrpDhJdTz-xeTRks5qfgtVgaJpZM4JgtG1 .

jetwhiz commented 8 years ago

@gzl6 if you use verbose mode (encfs -v d:\test x:), does it give any errors or useful output? The verbose logs will be stored in your %TEMP% folder.

gzl6 commented 8 years ago

1# Mount encfs -v d:\测试 x:, command window idle and no output on screen and %TEMP% folder 2# Mount encfs -v d:\test x: , screen as attached, And a new file of enc7C15.tmp, size 1KB content: 2016-08-19 11:05:06,570 VER [main.cpp:539] Closing stderr

ashampoo_snap_2016 08 19_11h06m23s_003_

jetwhiz commented 8 years ago

@gzl6 -- I'm going to have to look into supporting these languages ... right now the terminal is set to always use UTF-8, which might be causing these issues. Also, Dokany uses UTF-8 and UTF-16 internally.

Can you test out Dokany and see if you can successfully use their samples in these multi-byte languages?

gzl6 commented 8 years ago

I used mirror.exe to try. The result is OK.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

mishuha commented 5 years ago

Got issue like this on cyrillic folder naming in v1.11.0-beta.1 using GUI - "error saving configuration file". After folder was renamed accordingly to ascii the error has disappeared.

jetwhiz commented 5 years ago

It looks like stalebot got overly eager and closed this issue ... I've reopened this issue since it still needs to be addressed.