Jump to content

CoffeeCake

Clients
  • Posts

    1,916
  • Joined

  • Days Won

    24

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by CoffeeCake

  1. @wohali, I think @Lindy is misunderstanding your question. This is exactly how we download updates--we step through the installer, download them locally when given the option, and then put the files into our production server using our deployment mechanisms. We do not have sftp open to the world, and we manage code changes via git. We step through the updater, provide IPS credentials, and then click the link (look carefully for it) that says something like "I'll upload these changes myself."

    You will then get a zip file with delta changes in your browser (only the files that have changes to them), and can use whatever your process is to deploy those files.

    Alternatively, log into the Client Area and download the suite. This will include all files (not just those changed between the release you've deployed and the latest).

  2. 18 hours ago, Stuart Silvester said:

    such as requiring multi-factor authentication for AdminCP access.

    While you've got me on a rant, IPS will not use two-factor authentication for ACP access when providing support. This, while a really good idea, is required to be turned off by IPS or they cannot log in and we reach a standstill. So, this requirement has to be disabled for an account that IPS uses in the context of providing support.

    I can appreciate that finding a nice way for people around the globe to share TOTP tokens is a challenge, but it's not unsurmountable, and there are other great ways to confirm that the support person logging in has more than just the username and password.

    Edit: The constants.php guide probably could some references to where to read more about changing the constants listed there (For example, go look at init.php for details on others available and for notes on usage and associated warnings).

  3. As @Morrigan shared, the feature is marked as deprecated. See line ~295 in init.php:

    //--------------------------------------------------------------------------------------
    // DEPRECATED OPTIONS: CHANGE AT YOUR OWN RISK
    // These constants were once customisable but their fucntionality should now be
    // considered deprecated.
    				
    	// AdminCP Obscurity Settings
    	// It was once recommended for site owners to rename the directory for security
    	// and set the CP_DIRECTORY constant so some links still work, the upgrader can put
    	// files in the right place, etc. While it is still honoured, it is no longer recommended
    	// as much more secure alternatives like two factor authentication now exist.
    	'CP_DIRECTORY'	=> 'admin',	// The name of the directory where the AdminCP is

    If we're all cool leaving this exactly as is, maybe with bigger warnings, and flashing traffic cones and such, then all is right in the world.

    Im Out Amy Poehler GIF by FOX TV

  4. 17 hours ago, Stuart Silvester said:

    Security through obscurity isn't the best idea. We recommend using the built in tools instead such as requiring multi-factor authentication for AdminCP access.

    We also often see that customers that have done this still forget to rename the folder when upgrading manually and they end up with two admin folders, one that redirects to the other completely ruling out any obscurity advantage.

    Please don't deprecate this. Hide in the docs, put up big warnings if you must, warn people that there is no additional security by doing this by itself, but please leave the option intact. Security through obscurity is the reliance of hiding things on security and is bad news bears. However, having the admin control panel in a non-standard place is one of many layers of protection, upon which moving it is not relied upon for security.

    Consider Magento: https://docs.magento.com/user-guide/stores/store-urls-custom-admin.html

    Capturing and mitigating against attempts to access the default URL serves a honeypot of sorts (we identify and isolate attempts to hit /admin which would be coming from no one up to any good), helps protect against scripted attacks, and layered with other protections, serves as a multi-layered approach to security. We secure administrative things on multiple fronts, including moving the ACP address, protecting access behind zero trust authentication, and having separate accounts for elevated administrative functions. We monitor and block traffic attempting to access known paths that no legitimate user would have any business accessing (i.e. example.com/wp-admin/, /admin, etc.), but we protect the actual administrative things as if the URLs were known to all.

    The option to change the ACP path absolutely should come with a big "do not tamper with unless you know what you're doing" sticker. But please don't take it away.

  5. 9 hours ago, acarlsson said:

    1. Avatars are gone, and all embedded pictures are gone (replaced by question marks). The paths to these are set correctly, what have I missed?

    Edit: Example: Look at this page. Avatars and pictures are not there. If you hover the embedded pictures it says the URL should be /uploads/monthly... etc. I don't have any "monthly" folder in my uploads folder. And I didn't have it on the old forum either!?

    Did you copy the filesystem from your existing server to your test server before the upgrade? You need to restore both the files on the filesystem and the database.

    I'm not sure how things worked in 3.x, but with 4.x files are typically saved on disk.  You might have something like Amazon S3. Again, not sure how it worked in the 3.x branch.

  6. 9 hours ago, SecondSight said:

    - preventing these members from reporting anything ?

    You can do this. In member group settings, under content, there is a "can report content" feature. It's all or nothing, meaning if you take away the ability to report content, they won't be able to report any content.

    There is no built in functionality to make the content of a moderator/administrator unreportable (and I'm not sure I'd recommend enabling such a thing--it may be best to deal with the abusive member's behaviors directly).

  7. Just take multiple backups, and be sure that your backup is using the correct character set.

    I'm not sure about 3.x, yet you need to make sure that your 4.x backups are encoded with utf8mb4. Otherwise, any emojis in your posts will be forever lost in time. This is not the default behavior of most backup tools.

    https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb4.html

    This isn't mentioned in the above guide and probably should be. @Jordan Invision

    To make a backup with mysqldump, you'd want to do something like the following:

    mysqldump -u <yourmysqluser> -p <yourIPSdatabase> --default-character-set=utf8mb4 > mycarefullytakenbackup.sql

    You can never have enough backups.

  8. It sounds counterintuitive, but reduce the limits and make sure that everything with a limit matches. Your CDN, your web server, and PHP, as well as anything else (suhosin) that may be running on your server and interfering with uploaded files.

    IPS will chunk uploads into segments for files larger than your post max size. You do not need or want to set things to the maximum file size possible.

  9. Your server is likely underpowered and/or needs its configurations optimized. MySQL server goes away errors are typically related to timeouts. Timeouts happen when things take too long, and things take too long when they're not optimized or overloaded. You may consider using elasticsearch instead of MySQL for searches if the size of your community makes sense for that.

    Work with your web host to diagnose or take a look at some of the third-party providers that do this work for you if you cannot.

    https://invisioncommunity.com/third-party/providers/

×
×
  • Create New...