Hi flakes,

regarding FiSh.mrc:
I am trying to optimize & update the FiSh.mrc + making a little Gui for FiSh.

After some time I realized, that some variables are saved within mIRC (i.e. " set %mark_outgoing [On] " ), others instead are saved within the blow.ini-file (i.e. " writeini -n %blow_ini FiSH plain_prefix $1- ".
Does this have a particular reason?

Ok, not bad at all, but what I am trying to do is following:

• I try to make it possible (via Gui) to edit the "mark_encrypted"-variable within mIRC. But mIRC cannot write Color-Codes in a txt file (command: writeini or write). So right now - if you want to use a colored "mark_encrypted" - it is only possible to edit this variable through a text-editor.

Solution #1

I elaborated following workaround, if the "mark_encrypted"-variable has to stay in the blow.ini-file:
If you want to edit the variable within mIRC, use following command:
writeini -n %blow.ini FiSH mark_encrypted $chr(34) $+ $!chr(2) $!+ $!chr(3) $!+ 12 · $!+ $!chr(3) $!+ $!chr(2) $+ $chr(34)

output in blow.ini would be:
mark_encrypted="$chr(2) $+ $chr(3) $+ 12 · $+ $chr(3) $+ $chr(2)"

If you want then to evaluate this variable, just use Evaluation brackets (http://script.quakenet.org/wiki/Evaluation_brackets),
i.e. var %mark = [ [ $readini(%blow.ini,n,FiSH,mark_encrypted) ] ]

This method works fine with Crypt-Mark (Outgoing), but does not work so far with Crypt-Mark (Incoming). The last one would need a modified .dll I guess.

Solution #2

But I think the better solution would be as following:
Just save this variable (and all others except the keys) within mIRC, using i.e. " /set %mark_encrypted ". Because writing Color codes with set-command is absolutely possible.

What do you think? Is there really an important reason to leave those settings in the blow.ini-file?

After all, many thanks for your work. Your work is highly appreciated :-).

Kind regards,

Hello,

Can you update with latest openssl version?

Thx.

Found by December. Not sure to what extent we can fix this.

More explanation:

<jarod> flakes to be sure:

<jarod> home > ssl proxy > irc bouncer, fish10 does not work yet?

<jarod> ah thats sock5 i guess, so no worky

<flakes> yeah no worky on socks

<jarod> why?

<jarod> cant just copy old fish code? :P

<flakes> uhm

<jarod> or is it a mirc 7 thing?

<flakes> the old FiSH used to modify the mirc.exe file

<flakes> so it hooked in before the point where a proxy came into play

<jarod> ahyes

<flakes> I don't want to modify the exe file for each new mIRC version

<jarod> is it fixable?

<flakes> so I hook in later

<flakes> at which point I have to decide for every connection whether it's IRC, DCC, HTTP, $sockopen...

<flakes> ...and proxied connection look a lot different

<jarod> i see

<jarod> well i cant use it with

<flakes> so yes it is fixable, but it's a substantial amount of complexity to overcome

<jarod> ssl proxy > random ssl proxy > server > irc

<jarod> i guess when $sockopen is done, all beyond that should be good?

<flakes> mIRC > server > whatever and mIRC > bouncer > whatever works

<flakes> uhm no

<flakes> that's all working

<flakes> just proxies aren't, because those connections ARE IRC connections (where $sockopen etc. aren't)

<flakes> that's the hard thing to determine

<jarod> ya ok, but its a local proxy

<jarod> port 127.0.0.1

<jarod> err

<jarod> host

<flakes> doesn't matter

<flakes> on a normal IRC connection, the very first thing that goes over the wire is always "CAP LS" ... when SSL is used, another bit of data comes before that, but that's easy to recognize

<flakes> however, when a proxy is used

<flakes> it's the proxy protocol that encapsulates IRC. Or, even worse, proxy protocol encapsulates SSL which encapsulates IRC

<jarod> ah

<jarod> ok ok

I have some problems with umlauts like ä, ö, ü, or ß. These are encoded very strange and cannot be read by others. Additionally, I also receive strange characters if someone is writing umlauts.

Example:

A is using FiSH 10 with mIRC 7.1
B is using FiSH 1.30 with mIRC 6.35

B sends "gefällt" -> A receives "gef㫬t"
A sends "später" -> B receives "später"

Everything else works just fine, thanks so far! :)

http://fish.secure.la/forum/viewtopic.php?p=1778#p1778

Currently only on start we can see which version we have 'installed'.

Would be nice if we could see that via /fishdebug or even /fish -v or something similar :)
Even hardcoded version in context menu would suffice.

Thanks in advance for this lovely addon.

Changing the mark_encrypted value in the ini, saving, and then typing in a previously encrypted query resulted in a loss of encryption. I am going to look into this further as I wasn't the one who experienced this issue, however I was in conversation with them while it happened and witnessed it.

Hi,

I appreciate all your work with the new fish, but for some reason each time I attempt to install, I get a popup error that says it failed to load into memory. I have followed you instructions to the letter, but nothing seems to work.
Any ideas from you would be greatly appreciated. Again, thanks for all the hard work..

Hi,

OS: WinXP Sp3 german (VMware)
mIRC: v7.04 BETA
blow.ini: used the EXAMPLE shipped in the package

Installation works so far, but it cannot read keys from the blow.ini file?
I added Keys via "Set new Key" & "Set new Key (UTF-8)", blow.ini gets correctly updated (e.g. [QuakeNet:#test] ), but "Show key" just brings following message:
*** FiSH: No valid key for #test found

Also encryption does not work at all. It seems, that the command "$dll(%FiSH_dll,FiSH_GetKey10, $network %cur_contact)" does not work, because it brings you $null as result. But "Remove Key" works.

Also the prior release (mirc_fish_10-with-ssl-2010-05-20) just works fine on that machine.

I tested then the "fish testing build" in Win7 x64 (also VMware) with the same setup, and there it works. So I guess only XP is affected in some way?

Can someone approve that? Or did I something wrong?

Hello,

is it possible to add to your next version of fish10 , the CFB mode support ?

Thanking you

zer0c0nf

It doesn't send NETWORK with 005, so $network is empty. We should detect PsyBNC and try to use something like $crc($server $port, 0)

Is there a fix to get mirc_fish to work with the new Openssl?

Hello,

Can you update with latest openssl version?

Thx. ;-)

Introduce a new Alias=#copyfrom setting (don't allow recursions)

Hello guys,

I discovered following issue:
Example: You are connected to 2 irc-servers, and on each server you join #test

-> You cannot set a separate FiSh-Key for each #test -channel. The first FiSh-Key you set will be used for every #test -channel , regardless of its server.

I guess, that needs some further tweaking the "FiSH.setkey" / "FiSH_WriteKey"-routine, because this bug also exists in prior FiSh-versions (see http://fish.secure.la)

Hello,

Can you update with last openssl version?

Thx.

$ sha3sum mirc_fish_10-with-ssl-2017-02-25.zip
cbcfa6e4c3175d7e62d230d3fef72d54b8ffab05d42b516aa466c2af  mirc_fish_10-with-ssl-2017-02-25.zip

$ rhash -v --sha3-224 mirc_fish_10-with-ssl-2017-02-25.zip
Config file: /etc/rhashrc
Format string is: %{sha3224}  %p\n
cbcfa6e4c3175d7e62d230d3fef72d54b8ffab05d42b516aa466c2af  mirc_fish_10-with-ssl-2017-02-25.zip

tried downloading the file multiple times, from different connections

Noticed by maxm on the mIRC forums.

mIRC 7.25 has seemingly optimized the process of establishing IRC connections, thereby confusing FiSH 10's inner workings.

I am working on a new version that does not suffer from this problem, it will however take some days or weeks. It's going to get rid of the flawed logic and moreover possibly enable proxy support.

I will post any relevant progress to this bug.

UNTIL THEN, HERE IS A WORKAROUND:

• Use znc (IRC bouncer software) to connect to your networks. Connections through ZNC (be they SSL encrypted or not) do not seem to suffer from the problem.

Peace.

If a message is sent in a query between one computer running latest WinXP and latest Win7 (both english) there appears to be a bug on the side of the Win7 mirc client: every message ends with an  printed in blue color.

Both sides use a clean mirc v7.1 + newest mirc_fish_10.

I did all the steps and the first time it worked like a charm. But after i rebooted my pc all time i get this error: "FiSH 10 failed to load: Patching functions in memory were unsuccessful. Debug info: [00011011]".
The weird is that after i click ok on this message window, on mirc it says: *** FiSH 10 *** by [c&f] *** fish_inject.dll compiled Sep 28 2010 19:53:30 ***
*** FiSH 10 *** by [c&f] *** fish_10.dll     compiled Sep 28 2010 19:53:28 ***
But it does not work.
Any solution?

Hi.

I just installed mIRC 7.27 and newest fish (mirc_fish_10-with-ssl-2013-01-06.zip)
When I connect with psybnc, I cant set the key for channel nor private keyexchange.
There is no problem, if I connect without psybnc.

How can I fix this?

Best regards

for the right click menu

The code that is used for the ECB mode of operation does not honor the 56 byte (448 bit) maximum key length defined by the standard.

An application that truncates its key is unable to decrypt data output by mIRC FiSH 10 when the mIRC user configured a key that exceeds this length.

Edit: corrected incorrect bit length in message

I installed OpenSSL 32bit. I installed the visual c++ 2008 sp1 32-bit. I have done a clean install of mirc. I have loaded the script properly. It gives me a good start up message saying compiled on whatever date. It posts a [Test] or something to the blow.ini ... but for the life of me, I can't get it to save a key. Suggestions?

Hello,

Ive issue with new version of mirc.

Fish10 doesn't work anymore.

Thx!

The "if ($dll(%FiSH_dll,INI_GetBool,process_outgoing) == 0) return" call in the outgoing cryptmark code will return "0" if there is no process_outgoing setting defined in the blow.ini file. In order to provide a quick workaround, I've replaced the DLL call with a $readini call until the DLL call is updated to reflect this incompatibility, or the code for how the setting is defined is updated. The only problem with changing the process_outgoing setting to not use 0 as the off switch is that it will break all backwards compatibility. The following proposed code will fix the issue until another workaround is available.

START

;; !! The following call will return 0 if the process_outgoing setting is undefined in the ini
;; !! A temporary workaround of using $readini is the easiest solution until the code for the $dll call is updated
;if ($dll(%FiSH_dll,INI_GetBool,process_outgoing) == 0) return
if ($readini(%blow_ini,FiSH,process_outgoing) == 0) return

END

Replace the "if ($dll(%FiSH_dll,INI_GetBool,process_outgoing) == 0) return" line with the above code to enable outgoing cryptmarks again.

i keep on getting this

*** FiSH 10 *** by [c&f] *** fish_inject.dll compiled Apr 19 2012 18:10:42 ***
*** FiSH 10 *** by [c&f] *** fish_10.dll     compiled Apr 19 2012 18:10:41 ***
*** FiSH 10 *** WARNING: blow.ini is not writable! FiSH will not function correctly. ***

and nothing id decoded

MSL Hell awaits :(

I am unable to initiate a DH1080 keyXchange.

I am currently using: mIRC 7.22 via ZNC 0.098+deb2ubuntu1,

The only script loaded is the latest mirc fish 10 (2012-05-30).

[01:40pm] *** FiSH: Sent my DH1080 public key to xxxxx, waiting for reply ...

The keyXchange starts, but I never get a reply. If the other person initiates it, it works perfectly. All the other people I chat with are using irssi + fish module.

This is very frustrating, I don't want to have to downgrade mIRC and use the old fish modules.

1. Using mirc_fish_10-setup-2017-02-25.exe to update
2. Enter your path to mirc.exe here: "C:\Program Files (x86)\mIRC"
3. After clicking Next I get a Setup popup: mirc.ini file could not be located

- mirc.exe + ssl/fish10 dll's and mrc are in: C:\Program Files (x86)\mIRC
- mirc.ini + blow.ini are in: C:\Users\silver\AppData\Roaming\mIRC
- afaik these paths are used for the default way mIRC is installed nowadays.
- no portable flag set
- fish10 works fine with manual install from .zip

<---------FISH DEBUG---------
::VERSION
mIRC version: 7.47
SSL version: 1.0.2.8
SSL ready: $true
SSL mode: 1


::mIRC
mIRC dir: C:\Users\silver\AppData\Roaming\mIRC\
mIRC.exe: C:\Program Files (x86)\mIRC\mirc.exe
mIRC.ini: C:\Users\silver\AppData\Roaming\mIRC\mirc.ini
Portable: NotFound


::Files
fish_10.dll: "C:\Program Files (x86)\mIRC\fish_10.dll" - $true
version string: *** FiSH 10.2 *** by [c&f]  *** fish_10.dll     compiled Jun 15 2016 19:30:54 ***
fish_inject.dll: "C:\Program Files (x86)\mIRC\fish_inject.dll" - $true
version string: *** FiSH 10.2 *** by [c&f]  *** fish_inject.dll compiled Jun 15 2016 19:30:54 ***
blow.ini: C:\Users\silver\AppData\Roaming\mIRC\blow.ini - $true


::md5
fish_10.dll: 268adba46ec203edf1447b7549a9bbc7
fish_inject.dll: 8417d27881af45164667fe617aa52895
fish_10.mrc: dd6d5147cb2080cc6b71980039efc1f4


::Variables
blow_ini: C:\Users\silver\AppData\Roaming\mIRC\blow.ini
FiSH_dll: "C:\Program Files (x86)\mIRC\fish_10.dll"

Following error message pops up in mIRC at loading Fish 10: * /dll: unable to open file 'C:\PROGRA~2\mIRC' (line 20, fish_10.mrc)

This ONLY happens if the directory I installed mIRC to has spaces in the mIRC folder name.
For example:
This WORKS: C:\abc\mirc OR C:\abc\de fg\mirc OR C:\abc\de fg\mirc7.1
This DOESNT WORK (and the error message above pops up): C:\abc\mirc 7.1 OR C:\abc\mirc 7

I tested mIRC 7.1 with Fish 10 on 3 different computers all runing Windows 7 64Bit and a clean mIRC 7.1 installation and this error happens on all 3 computers. For now I installed it to C:...\mIRC7.1 but normally i would use C:...\mIRC 7.1 as folder name so it would be nice if you fix this error.

Sorry, I accidently closed the other one...

I'm running Windows 7 Ultimate and using Mirc 7.02.

I tried using both, but neither of them worked. Hope we can get this worked out.

I've downloaded mirc_fish_10-with-ssl-2012-06-14.zip and have a fresh install of mIRC 7.25 and fish is not working, I've copied all the dll/script files to %appdata%\mIRC and where mirc.exe is and no luck..

Implemented with #44, lots of complaints. Add option to ini file.

Hi,
can you build another SSE build for older CPUs?

I get this error with fish_10/2014-08-25 on an SSE machine:

• /dll: unable to open file 'D:\Programme\mIRC\fish_inject.dll' (line 18, fish_10.mrc)

I checked the dll and it holds SSE2 opcodes indeed:
.text:10001B65 movq xmm0, qword ptr [ecx-8]

Hi,

I think I discovered another problem. Seems when receiving a d/l from someone when it reaches 99% it stops and just hangs there. When I tried after removing the new fish, they complete fine.

Any ideas on this one??

Hello,

Can you update with latest openssl version, 1.1.0?

Thx. ;-)

I just downloaded the latest installer and when I ran it:
Step 1: http://imgur.com/eYZxOBc
Error: http://imgur.com/Vuldmvb

We cant install fish10 with a non-standard path... Why ?

Thanks for your time and support!

mIRC 7 sends the key in UTF-8, earlier versions received it in CP_ACP, need to make Set Key behave like the old versions and add Set Key (UTF-8) for UTF-8.

Getting this error in WindowsServer 2008:

* Loaded script 'C:\mIRC\fish_10.mrc'

• /dll: unable to open file 'C:\mIRC\FISH_I~1.DLL' (line 20, fish_10.mrc)

Technical infos:

• OS: WinXP german (VMware)
• mIRC: v7.04 BETA
• FiSh: mirc_fish_10-with-ssl-2010-06-12.zip
• blow.ini: used blow.ini-EXAMPLE shipped in above-mentioned test build

Hi flakes,

I recognized following issue with the newest test-build:
When I want to use "Set Key" in a channel or in a private-chat, then FiSh saves 2 entries for that regarding contact. One with $network and one without it.

Example:

Network: Quakenet
Channel: #test
using Set Key, blow.ini will then save those 2 entries:

[QuakeNet:#test]
key=+OK TaFzr0u6b3U1
date=12/06/2010
[#test]
key=+OK TaFzr0u6b3U1
date=12/06/2010

This also happens, when I just execute this command:
$dll(%FiSH_dll,FiSH_WriteKey10,$1 $network #test some.test.key)

Because of that multiple server support in FiSh does not work.

Can someone approve that?

Hello,

Can you update with latest openssl version, 1.0.2n?

Thx. ;-)

Seems fish10 stops working for mirc 7.49. Everything loads up fine without errors, dll's are loaded and /fishdebug looks ok, the hello world/blow.ini check at the end too. Keys are also loaded (FiSH.showkey), key exchange works. But messages/topics are not decrypted.

Switching back to the 7.48 mirc.exe solved the problem.
Using openssl 1.0.2k.

"Local" channels with &chan instead of #chan (fine with RFC) do not get their topics decrypted. The code shows why, and also points to a possible future solution ("keep track of local nickname and use that to determine message type (channel or query)")

The latest version (mirc_fish_10-with-ssl-2013-09-23.zip) contains SSE2 code that doesn't work on (SSE1 only) CPUs like AthlonXP (K7). 'fish_10.dll' crashes with exception 0xC000001D.

On GCC you can fix that by using compiler flags like this:
-march=pentium3 -mfpmath=sse -mno-sse2

hello trying to set copy local ip to clipboard and it comes back blank.

tried several times to get thsi to work with no joy using mirc 7.27 and fish 10

*** FiSH 10.2 *** by [c&f] *** fish_inject.dll compiled Jun 25 2012 00:06:13 ***
*** FiSH 10.2 *** by [c&f] *** fish_10.dll     compiled Jun 25 2012 00:06:12 ***
*** FiSH 10 *** WARNING: blow.ini is not writable! FiSH will not function correctly. ***

Hello!

Can you update to latest openssl version?

Thx,

zc0nf

Example:
PRIVMSG #one,#two,#three,#four :Hi!

Damn...

Must be compatible to Mircryption: http://www.donationcoder.com/Software/Mouser/mircryption/extra_cbcinfo.php