Xenforo 2.2 release

Status
Not open for further replies.
If you want to be really picky, there are exposed tokens parsed via URLS in plain text, which could be considered a security issue BUT those tokens don't expose any identifying information.

Only thing I'd like to see is a way to lockdown Admin Control Panel, whereby attempts to login, result in a blacklisted / blocked IP address.

I'd also recommend changing the default phrase "incorrect_password" to something like:
Code:
<p>Username not found or Incorrect Password.</p>
<p>Please try again. If you believe this is in error, please contact us.</p>
<p>This error has been logged.</p>

This way it never confirms (like it does by default) that a username is correct, but password is not.

I hate sites who do that. Some don't even confirm if you entered correct email and you're left guessing if you enter wrong email or their email isn't delivering/ending up in spam box.

That's not security. That's just crap user experience. Lock an account if more than x number of tries in x amount of time and problem solved. Lock the login pages behind cloudflare maximum security and no bot can access it = no bruteforce.
 
I hope 2.2 will take speed (even) more serious.
For example, the FA icons (woff2) take way too long to load imo.

The default theme should be as fast as possible but maybe more important, 3rd party themes should be as fast as possible too. I hope there is a way to "force" developers to use certain templates/workflows/whatever to ensure loading times are as fast as possible.

I like the XF approach. The default install is lean and mean and can be extended with add-ons.

The downside of that approach is the dependability on 3rd party developers. That can result in problems during upgrades. Would be nice if that dependability can be reduced somehow.

I agree. Especially with Google planning to punish/rank sites based on Pagespeed recommendations, it should be priority number one.

I managed to get my wordpress site score to 95 mobile/97 desktop with a simple plugin and it would be safe when Google implements that change next year.

I don't know if any such addons exist for xenforo and the scores for stock xenforo aren't that great.

I actually made a thread and it received no love which shows people probably don't even know or care about it.
 
I hate sites who do that. Some don't even confirm if you entered correct email and you're left guessing if you enter wrong email or their email isn't delivering/ending up in spam box.

That's not security. That's just crap user experience. Lock an account if more than x number of tries in x amount of time and problem solved. Lock the login pages behind cloudflare maximum security and no bot can access it = no bruteforce.

To clarify we are only talking about the backend /wp-admin here.
That's the idea. Yes it's security by obscurity to a degree, but it lessens brute force attempts/account hijack attempts as there is no confirmation that the account even exists. It's not the site owners fault if people can't remember a username/password.

In fact it's a recommendation from security companies and Wordpress as well.

Not everyone uses Cloudflare and it's certainly not the be all and end all (infact for local AU users it slows your site down unless you have an expensive paid plan with a local POP).

I agree. Especially with Google planning to punish/rank sites based on Pagespeed recommendations, it should be priority number one.

I managed to get my wordpress site score to 95 mobile/97 desktop with a simple plugin and it would be safe when Google implements that change next year.
I don't bother with Google Pagespeed as it has a long and documented history of being highly inaccurate compared to sites like GTmetrix.com.

Stupid stuff like "you got marked down because your js and css isn't minified", and yet it is. Or "not mobile friendly", yet the entire site is mobile responsive and clean as.
 
That creates a Denial of Service attack vector, which is why it is not done.
Yep as you are effectively admitting that user account exists.

What STNN is proposing is akin to securing your house by having locks on the external doors, rather than standard door knobs. It's unlikely to stop most criminals because you are still responding as to if an account exists.

You never want to confirm on a login page that a username is indeed valid or invalid, as once that is determined, they know the password is the only thing they need to work on. That's 50% of your way to an intrusion (even if you aren't attempting to brute force a login page), as you can potentially use that username to authenticate not just with the admin login page.

The other reason it's annoying and account lockouts are not smart, is you can have a nefarious user who takes issue to another user. They deliberately try to log in several times just to lock that other users account out.

Sure I realise that most breaches these days are shifting towards injection attacks, exploits, and backdoors, but if you aren't responding to any username/password combination, it makes any attempt to brute force completely useless.
 
I don't bother with Google Pagespeed as it has a long and documented history of being highly inaccurate compared to sites like GTmetrix.com.

Stupid stuff like "you got marked down because your js and css isn't minified", and yet it is. Or "not mobile friendly", yet the entire site is mobile responsive and clean as.

I agree with you. I think it's utter garbage but Google brings us traffic and we have to play by their rules. I hope they don't implement it ever.
 
I agree with you. I think it's utter garbage but Google brings us traffic and we have to play by their rules. I hope they don't implement it ever.
Funny thing with Google is they do all this crap, and yet fail to act on sites that are SEO scam/spam sites. Punish the good guys and let the bad guys continue.

Probably one for another topic though :D
 
The important
When is the date of issue?

How can they tell? They can only give an estimate but can not tell for sure. They did say it will be this year barring any unforeseen circumstances.

Coding is an extremely complex process especially at this level then ensuring it meets the quality guidelines, security, bugs etc. I hope XF takes as much time as they need so we don't have to deal with a broken forum.
 
I am quite surprised not many people (if any) are requesting WYSIWYG editor on pages backend..? :whistle:

My "Want" list includes:
  • Auto-close topics (based on criteria such as time, prefix etc)
  • WYSIWYG Editor on Pages
  • Ability to restrict access to the dashboard to IP
  • Poll permissions - restrict creation of polls per user group
 
I am quite surprised not many people (if any) are requesting WYSIWYG editor on pages backend..? :whistle:

This is not the right thread or forum for requests/suggestions, you need to like the first post here:

 
I am quite surprised not many people (if any) are requesting WYSIWYG editor on pages backend..? :whistle:
Pages and custom fields are probably the least developed aspect of XF and both are crucial for content delivery. We have already tons of moderator tools, if not for everything an addon. Whereas content focused stuff is underdeveloped or non-existent.

We need so much more for content creation. Content brings people to your sites, not "auto-close topics" as a tool. Sure, I agree that an auto-close option would be nice to have (like many more things which is just not there), but we are lacking more important stuff then these stuff.

It is June and still no news. Even if we get the long awaited news, the wait is so long that the expectations are growing bigger and bigger. We'll see I guess.
 
I am quite surprised not many people (if any) are requesting WYSIWYG editor on pages backend..? :whistle:
Xenforos power is in being complex yet simplistic. It's complex areas generally don't break the simplistic things.

When you start integrating (often bloaty) WYSIWYG editors for pages, that can change things greatly.

I like the 10-15MB download and install package, and would rather not see it a 150MB download and install package for lesser used features.

Easier to just jump into an online HTML editor, fire it up and format your page as you like (ensuring it complies with HTML5 standards), and then just copy/paste the code into pages.

When will 2.1.11 be ready? 😄
Hold the boat we haven't got to v2.1.10.3 yet!
 
Xenforos power is in being complex yet simplistic. It's complex areas generally don't break the simplistic things.

When you start integrating (often bloaty) WYSIWYG editors for pages, that can change things greatly.

I like the 10-15MB download and install package, and would rather not see it a 150MB download and install package for lesser used features.

Easier to just jump into an online HTML editor, fire it up and format your page as you like (ensuring it complies with HTML5 standards), and then just copy/paste the code into pages.


Hold the boat we haven't got to v2.1.10.3 yet!
A WYSIWYG editor (froala) is already included in the package (I am using it right now to write this message) so I believe it would be extremely easy to implement. I think XF developers have their own reasons for not adding this and it's definitely not related to coding or bloating etc. Maybe they want to keep that platform purely as a forum software and I completely understand that. If you start adding CMS features you open the door for more bugs and problems since people will most probably start using it tobuild non-forum sites.
 
I just hope they don't cram it with too much bloat. Best to keep the basic forum software light and then provide the rest as options you can purchase.
 
XF 2.2 HYS cycle?

MondayTuesdayWednesdayThursdayFridaySaturdaySunday
Jun 1Jun 2Jun 3Jun 4Jun 5Jun 6Jun 7
Jun 8Jun 9Jun 10Jun 11Jun 12Jun 13Jun 14
?
Jun 15Jun 16Jun 17Jun 18Jun 19Jun 20Jun 21
???
Jun 22Jun 23Jun 24Jun 25Jun 26Jun 27Jun 28
???
Jun 29Jun 30Jul 1Jul 2Jul 3Jul 4Jul 5
???
 
XF 2.2 HYS cycle?

MondayTuesdayWednesdayThursdayFridaySaturdaySunday
Jun 1Jun 2Jun 3Jun 4Jun 5Jun 6Jun 7
Jun 8Jun 9Jun 10Jun 11Jun 12Jun 13Jun 14
?
Jun 15Jun 16Jun 17Jun 18Jun 19Jun 20Jun 21
???
Jun 22Jun 23Jun 24Jun 25Jun 26Jun 27Jun 28
???
Jun 29Jun 30Jul 1Jun 2Jun 3Jun 4Jun 5
???
So why are we going from July 1st back to June 2nd? :unsure:
 
Status
Not open for further replies.
Top Bottom