Skip to content
This repository has been archived by the owner on Oct 9, 2019. It is now read-only.

FiSH support #215

Closed
hlx98007 opened this issue Oct 5, 2017 · 7 comments
Closed

FiSH support #215

hlx98007 opened this issue Oct 5, 2017 · 7 comments
Labels

Comments

@hlx98007
Copy link

hlx98007 commented Oct 5, 2017

I searched within the issue section and found no answer, will it be FiSH/blowfish support in the future?

Thanks.

@Mikaela
Copy link
Collaborator

Mikaela commented Oct 5, 2017

I would say no as I haven't ever seen it used anywhere during my years of IRC usage and I consider server links being SSL enough.

I am not closing this yet in case @FruitieX considers this to be within the scope of TeleIRC.

@adedomin
Copy link
Contributor

adedomin commented Nov 4, 2017

pretty sure FiSH is insecure, especially in this era. if you want support for some symmetric crypto it would be possible.... but why? it will be emitted in plaintext over telegram since group chats aren't encrypted using any exchange i know of.

@hlx98007
Copy link
Author

hlx98007 commented Nov 4, 2017

@adedomin FiSH is a secure algorithm to date. I am trying to read off from an encrypted IRC channel to TG.

Problem is teleirc does not support network login capability, otherwise I would use ZNC to workaround the need & issue.

@Mikaela
Copy link
Collaborator

Mikaela commented Nov 6, 2017

Problem is teleirc does not support network login capability, otherwise I would use ZNC to workaround the need & issue.

What do you mean with network login capability? I am using TeleIRC with SASL without issues (which ZNC doesn't support though), but I think that it's possible to send server password without SASL too which would be what ZNC wants.

// see https://node-irc.readthedocs.org/en/latest/API.html#client for
// documentation
config.ircOptions = {
userName: 'bot',
realName: 'Telegram IRC Bot',
port: 6667,
password: '',
localAddress: null,
showErrors: false,
autoRejoin: false,
autoConnect: true,
channels: [], // auto generated, do not touch
secure: false,
selfSigned: false,
certExpired: false,
floodProtection: true,
floodProtectionDelay: 1000,
sasl: false,
stripColors: true,
channelPrefixes: '&#!',
messageSplit: 512,
encoding: ''
};

@hlx98007
Copy link
Author

hlx98007 commented Nov 6, 2017

@Mikaela
Copy link
Collaborator

Mikaela commented Nov 6, 2017

@hlx98007 As far as I am aware that is what password under config.ircOptions does.

password: '',

See also my previous comment for more details.

@hlx98007
Copy link
Author

@Mikaela Thanks for the note, it looks like this is indeed passing PASS command to znc, the doc and example config did not include this and that was my bad for not reading the doc carefully.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants