1:48 p.m.
just a heads up that I have not been able to connect to freenode for quite
a few weeks now. Still no idea what is up there.
2:34 p.m.
On 13 Oct 2014, at 20:48, Steve Ebersole wrote:
just a heads up that I have not been able to connect to freenode for
quite
a few weeks now. Still no idea what is up there.
freenode moved to require SSL for some connections afaik. Use 6697 for
port,
and they also changed hostsnames - thus use irc.freenode.org if you
don't already
And finally the one that annoyed me in US last time I was there. AT&T
customers
cannot connect unless using SASL (https://freenode.net/sasl/) - maybe
they extended
that to other providers ?
just some ideas.
/max
http://about.me/maxandersen
3:31 p.m.
I had trouble too after I changed passwords as recommended; I decided
to give client side certificates a go:
https://freenode.net/certfp/
Works far better now and I have no longer clear text passwords; Also I
can finally have it connect to #hibernate-dev automatically as it
properly authenticates before trying to join.
Using Konversation.
Sanne
On 13 October 2014 20:34, Max Rydahl Andersen <manderse(a)redhat.com> wrote:
On 13 Oct 2014, at 20:48, Steve Ebersole wrote:
> just a heads up that I have not been able to connect to freenode for
> quite
> a few weeks now. Still no idea what is up there.
freenode moved to require SSL for some connections afaik. Use 6697 for
port,
and they also changed hostsnames - thus use irc.freenode.org if you
don't already
And finally the one that annoyed me in US last time I was there. AT&T
customers
cannot connect unless using SASL (https://freenode.net/sasl/) - maybe
they extended
that to other providers ?
just some ideas.
/max
http://about.me/maxandersen
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
10:48 a.m.
"works better" how? You mean as in more stable? I can connect now using
the info from Max (thanks Max!). But I keep having "no response from
server" type connectivity problems. Wondering if certs would help there.
I don't see how.
On Mon, Oct 13, 2014 at 3:31 PM, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
I had trouble too after I changed passwords as recommended; I
decided
to give client side certificates a go:
https://freenode.net/certfp/
Works far better now and I have no longer clear text passwords; Also I
can finally have it connect to #hibernate-dev automatically as it
properly authenticates before trying to join.
Using Konversation.
Sanne
On 13 October 2014 20:34, Max Rydahl Andersen <manderse(a)redhat.com> wrote:
> On 13 Oct 2014, at 20:48, Steve Ebersole wrote:
>
>> just a heads up that I have not been able to connect to freenode for
>> quite
>> a few weeks now. Still no idea what is up there.
>
> freenode moved to require SSL for some connections afaik. Use 6697 for
> port,
> and they also changed hostsnames - thus use irc.freenode.org if you
> don't already
>
> And finally the one that annoyed me in US last time I was there. AT&T
> customers
> cannot connect unless using SASL (https://freenode.net/sasl/) - maybe
> they extended
> that to other providers ?
>
> just some ideas.
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
11:54 a.m.
On 14 October 2014 16:48, Steve Ebersole <steve(a)hibernate.org> wrote:
"works better" how? You mean as in more stable? I can
connect now using
the info from Max (thanks Max!). But I keep having "no response from
server" type connectivity problems. Wondering if certs would help there. I
don't see how.
Yes I have the impression that it's more stable, but have no facts backing that.
The main reason for me to like certs is not stability though, but it's
the "login first" semantic, as I'm otherwise kicked out of
#hibernate-dev.
Sanne
On Mon, Oct 13, 2014 at 3:31 PM, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
>
> I had trouble too after I changed passwords as recommended; I decided
> to give client side certificates a go:
> https://freenode.net/certfp/
>
> Works far better now and I have no longer clear text passwords; Also I
> can finally have it connect to #hibernate-dev automatically as it
> properly authenticates before trying to join.
> Using Konversation.
>
> Sanne
>
> On 13 October 2014 20:34, Max Rydahl Andersen <manderse(a)redhat.com> wrote:
> > On 13 Oct 2014, at 20:48, Steve Ebersole wrote:
> >
> >> just a heads up that I have not been able to connect to freenode for
> >> quite
> >> a few weeks now. Still no idea what is up there.
> >
> > freenode moved to require SSL for some connections afaik. Use 6697 for
> > port,
> > and they also changed hostsnames - thus use irc.freenode.org if you
> > don't already
> >
> > And finally the one that annoyed me in US last time I was there. AT&T
> > customers
> > cannot connect unless using SASL (https://freenode.net/sasl/) - maybe
> > they extended
> > that to other providers ?
> >
> > just some ideas.
> >
> > /max
> > http://about.me/maxandersen
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
6:04 p.m.
I don't see how it could be related but a few weeks ago freenode
recommended that everyone change their passwords.
On 10/13/2014 02:48 PM, Steve Ebersole wrote:
just a heads up that I have not been able to connect to freenode for
quite
a few weeks now. Still no idea what is up there.
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
3:27 p.m.
Found this link on Hacker News:
https://www.nccgroup.com/en/blog/2014/10/analysis-of-the-linux-backdoor-u...
Apparently they were hacked pretty badly.
On 10/13/14, 7:04 PM, Scott Marlow wrote:
I don't see how it could be related but a few weeks ago freenode
recommended that everyone change their passwords.
On 10/13/2014 02:48 PM, Steve Ebersole wrote:
> just a heads up that I have not been able to connect to freenode for quite
> a few weeks now. Still no idea what is up there.
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
1:50 p.m.
Interesting. I think I may have found a big culprit. It seems that Fedora
likes to enable IPv6 on connections by default. I disabled IPv6 support
and some "unrelated" browsing problems I have been having were cleared up.
I'll have to see if that helps with IRC.
On Tue, Oct 14, 2014 at 3:27 PM, Thomas Jones-Low <
thomas.jones-low(a)foundationdb.com> wrote:
Found this link on Hacker News:
https://www.nccgroup.com/en/blog/2014/10/analysis-of-the-linux-backdoor-u...
Apparently they were hacked pretty badly.
On 10/13/14, 7:04 PM, Scott Marlow wrote:
> I don't see how it could be related but a few weeks ago freenode
> recommended that everyone change their passwords.
>
> On 10/13/2014 02:48 PM, Steve Ebersole wrote:
>> just a heads up that I have not been able to connect to freenode for
quite
>> a few weeks now. Still no idea what is up there.
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
3723
days inactive
3725
days old
7 comments
5 participants
participants (5)
-
Max Rydahl Andersen -
Sanne Grinovero -
Scott Marlow -
Steve Ebersole -
Thomas Jones-Low