Software :: Cannot Connect To FreeNode Via TOR Using SASL?
May 30, 2010
I tried to connect to FreeNode via TOR and directed to this web site.I have registered and verified by nickname with nickserv on FreeNode.Then I downloaded the XChat SASL plugin from here.I set it up the way it told me to.When I try and connect to the hidden service I am rejected being told I need to use SASL. What could I have done wrong and how can I find out>
why irssi won't connect to freenode (I am in the process of configuring it and username has been set).
Code:
15:09 -!- Irssi: Looking up irc.freenode.net 15:09 -!- Irssi: Connecting to irc.freenode.net [xx.xx.xx.xx.] port 6667 15:12 -!- Irssi: Unable to connect server irc.freenode.net port 6667 [Connection timed out]
My network connection seems fine. I have not any issues at all with ethernet/wireless so I am not sure what is causing this. Irssi worked fine on fedora before switching to arch.
I'm trying to connect to freenode using my Empathy but it always gives me network error (on chat.freenode.net and irc.freenode.net). The steps I took were the simplest ones: Edit > Accounts Add...Protocol: IRC Network: FreeNode Nickname: pedrosanta Real Name: Pedro Santa Start session This is very, very strange. Anyone got this too? Can you shed me some light on what's happening or how can figure that out? FYI, I'm using the Portuguese version.
With the latest Freenode changes SSL connection is now possible which presents no problem, particularly with rworkman's ca-certificates slackbuild, But configuring sasl for the password to nickserv presents a bit more of a challenge as 3 perl modules are required: Crypt::OpenSSL::Bignum, Crypt::DH, Crypt::Blowfish and Math::BigInt. I have not packaged perl modules for slackware before and I guess there is always a first time but can I ask if anybody has already neatly packaged up the required perl modules? I suspect they will be very popular with Freenode slackware irc users...
I am having some trouble with Cyrus SASL and OpenLDAP. I tried to configure OpenLDAP using SASL for all conection but I cannot map the SASL-DN to OpenLDAP's DN. Below is my configuration file, slapd.conf
[code]...
After I finished the configuration, I try to use ldapsearch tool to verify, but I cannot:
I installed webmin + postfix + dovecot + sasl2-bin to get a webserver running. I have fixed all the problems, but there is still one. I am totally new to sasl, so I am sorry if I made a stupid mistake.
[Code]....
Thunderbird gives the following error when trying to send mail: Sending of message failed. The message could not be sent because the connection to the SMTP server mail.virovene.org was lost in the middle of the transaction. Try again later or contact your network administrator. mail.err Apr 28 23:33:18 virovene postfix/smtpd[6264]: fatal: no SASL authentication mechanisms
I am attempting to enable secure authentication on my homebrew AWS based mail server, by following the very excellent flurdy how-to.However I think the repositories I am attempting to use do not include this software.Oddly enough, an aptitude search finds the packages I want, however even if I copy-paste the name of the software into the install version of the command it turns up nothing.
Code: root@cloud1:~# aptitude search sasl2-bin i sasl2-bin - Cyrus SASL - administration programs for SASL users
I need define a user /password for sasl but want the authentication at runtime be automatic - no explicit prompting the user while accessing a tcp socket with some applications that need the authentication (e.g libvirt)
so I try : saslpasswd2 -c -p -a libvirt <user>
and it hangs (if i now press Enter it says : "invalid parameter supplied") . if I avoid the -p flag the above commad works fine and prompts for password and later when using the tcp it prompts for the above defined user/password and autheticates ok . But I want without the explicit authentication
The man pages says -p Pipe mode - saslpasswd2 will neither prompt for the password nor verify that it was entered correctly. This is the default when standard input is not a terminal.
In the past (before some upgrading of libvirt via rpm) I had the SASL authentication at runtime done automatically with no explicit prompting the user
I'm getting relay access denied to an email outside of my domain. It seems the passwords are authenticating because I'm not getting invalid password prompts.
I've managed to get my Fedora box authenticate to AD with NSS_LDAP module with SSL working. I would like to bring this authentication to the next step by using SASL /GSSAPI, however I find very little / no documentation exist on this topic? I was wondering does anyone know where I can get the documentation on how to setup NSS_LDAP talking to AD with SASL/GSSAPI?
I have Postfix up and working perfect. It receives and sends email fine with no TLS and SASL but I installed Dovecot and then generated some self signed certificates using 'openssl' and for some reason I can't send from my IMAP server. I get this in my logs:
Code: Mar 3 11:20:45 mail dovecot: imap-login: Login: user=<carlos>, method=PLAIN, rip=10.1.1.204, lip=192.168.0.200, TLS Mar 3 11:21:20 mail postfix/smtpd[1386]: connect from tuna.mydomain.tld[10.1.1.204]
I have an issue where postfix is setup to use dovecot auth and as far as I know it works, if i login using telnet to the mail server i can authorize myself y providing the base64 encoded user & password. so if i can login, why cant my email clients. have tried thunderbird and evolution. this is the mail.log relavant entries for sucessful login via telnet
[Code]...
Login by pop or imap works flawlessly that what i dont get. From what i see it SHOULD be working. It it changes things, im using postfixadmin, postfix, dovecot. passwords and info stored in mysql tables. passwords are md5 encrypted. I thought that may be the issue, but that dosnt make sence.
I checked relay system using IP address it working gr8, but I want to implement user based authorization in relay server. but no idea where to make changes in sendmail.mc.. and my outlook asking for password again and again..whats role of openssl in user based authentication ?
I for some reason can't get Cyrus-sasl to work completely. I have to manually start it via saslauthd -a show if I let it start up itself or do a service saslauthd start or restart testsaslauthd will fail. I need help getting this fixed. I tried setting /etc/sysconfig/saslauthd to shadow instead of Pam but still no luck. Also when I try to login my postfix server I get an error stating that my username or password is incorrect even though it is right and I can receive mail from dovecot.
I have sendmail setup with sasl and multiple domains.I'm sure there is an easy fix for this but I can send emails to anyuser@<anyofmyvirtualdomains.dom> and it will be accepted. I'm just trying to cut down on any confusion that may occur later. Is it possible "restrict" or classify a user into a particular domain? I've setup virtusertable and aliases but no luck in accomplishing my goal.I've searched to find no particular information on this.
I'm trying to expand my Courier+MySQL+Postfix+PostfixAdmin server to use SASL logins on Postfix so I can relay on my server. After following several guides I still can't get it to work: Postfix logs show the user transcript and end with "Authentication failure" but it does not tell me what told it that the login failed. The messages log show this:
Feb 19 22:48:55 sportlaan-server saslauthd[7254]: do_auth : auth failure: [user=berend] [service=smtp] [realm=mydomain.com] [mech=pam] [reason=PAM auth error] Which I don't get because I don't think it should be using PAM... I think...
The setup is similar to this one: http://www.howtoforge.org/virtual_users_postfix_courier_mailscanner_clamav_centos_p6 My SASL config has this in it: /usr/lib/sasl2/smtpd.conf pwcheck_method: saslauthd log_level: 3 authdaemond_path: /var/spool/authdaemon/socket mech_list: plain login
We have CentOS 5.3 and are using sendmail for outbound emails. We are trying to switch over to authsmtp service. Authsmtp requires sendmail built with SASL suport.
How do I find out if my sendmail has been built with SASL support? If it is not, is it easy to build it with SASL support?
I just went through a painful upgrade from 8.04 to 10 LTS. I've made a lot of progress but am still having email problems. Dovecot seems to not be able to run, the log is continually reporting:
Aug 22 23:47:34 amd64 postfix/smtpd[22298]: fatal: no SASL authentication mechanisms
I'm using postfix with unix accounts for a while now and I just realized today that SASL authentication, instead of working only with the USERNAME, it also works if the username is followed by ANYDOMAIN.COM
So, let's say I have the following UNIX users: tim, mike, john. If I set the Outgoing Username:[URL]..(where whatever.com can be any name you can think of) IT WORKS, even though it shouldn't, it should only work with tim, mike and john without any domain name. Does anyone know what might cause this and what's the workaround to this problem?
When I send an email via TLS I see the following log entries.
Code: Oct 14 11:53:06 ns2 postfix/smtpd[11372]: connect from unknown[172.16.1.159] Oct 14 11:53:06 ns2 postfix/smtpd[11372]: setting up TLS connection from unknown[172.16.1.159] [Code]....
What I'm really curious about is there is an intial TLS connection with a 256 bit cipher, but then.. The last entry states "sasl_method=PLAIN" - so surely this is not encrypted? Or am I misunderstanding how it works?
I am re setting up a server of mine running red hat enterprise Linux server 6 and I had all of this working befor but for some reason I had troubles getting sasl to work and now when I login my smtp server I get an error stating that my username or password is incorrect though I am sure I am entering both correctly. Would anyone know what could be happening? I have been spending days on the web looking for the solution and only went from sasl not working when started as a service to this. For some reason I can't use Pam with saslauthd and had to use shadow instead of which from what I hear I get to use better methods of secure authentication with smtp
Slackware 13 64 - full installation Postfix from slackbuilds dot org Dovecot from same
has anyone recompiled Postfix using the Slackbuild script, modifying the script to include support for Cyrus-SASL, OpenLDAP, and MySQL in the build, while retaining Dovecot SASL and TLS? If so I would appreciate it if they could post the CCARGS and AUXLIBS commands. I am having some difficulty getting this working.