-
Notifications
You must be signed in to change notification settings - Fork 13.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auxiliary failed: ArgumentError invalid byte sequence in UTF-8 #15044
Comments
@adfoster-r7 I understand there are a lot of ascii and utf-8 issues with other languages. Are there any workarounds or planned fixes soon? |
@acheong08 We have been making some progress towards fixing these types of errors however as it stands the current case is that some areas of the framework are hardcoded to use ASCII over UTF-8, others prefer UTF-8 vs ASCII, and some can accept either. Trying to fix this completely will likely take some time as there are lots of side effects to consider if we want a complete and accurate fix without introducing odd behavior. For this particular case it would appear that either the
Even then that line doesn't actually do anything r.e the encoding as we can see from the example below:
Seems the issue is somewhere within the |
Thanks for taking a look Grant; Might be a regression in the rex-tables that should be fixed. I've created an internal ticket for this sprint 👍 |
Hi @acheong08 Unfortunately I wasn't able to replicate this issue. We'd appreciate if you would be able to confirm some information, could you provide more details on the host machine and terminal configuration you were using. Could you please try this command and let send a screenshot of your output please, just so we can compare. Could you also run If we could get these details, it may help us investigate this issue further. Thanks |
From wireshark capture: |
Just wanted to add that this happens in
|
Problem appears in non-English windows versions |
For what it's worth: I encountered this on my Kali, while browsing an xubuntu machine. |
I met the same problem in my kali system. How do you solve it ? |
@bcoles @skullcat2008 It's been a while, but I can't remember managing to fix this issue. |
Is your issue with the |
@bcoles For me it was just listing files from a directory and recursively downloading that directory when in a session to the remote machine. So maybe not the exact same issue, but maybe there is some kinda common encoder used across the entire framework? That affects several parts? |
It is unlikely to be the same issue. There are many. The original issue in this thread describes as issue in You mentioned:
I think those have been fixed. But there may be more. |
@bcoles Ok. Then I'm sorry for hijacking this thread and will stop. |
The crash should be fixed in the next release by #16729. If this is still an issue after using this release, which went out yesterday, then feel free to open this again. |
Steps to reproduce
How'd you do it?
Expected behavior
Return Chinese characters
Current behavior
Metasploit version
Framework Version: 6.0.40-dev-aaf27d7fa51390895dea63c58cb3b76e959d36f8
###Additional Information
It works with
set CMD cmd.exe /c echo <English_Characters>
The text was updated successfully, but these errors were encountered: