Megatools allow you to copy individual files as well as entire directory trees to and from the cloud. You can also perform streaming downloads for example to preview videos and audio files, without needing to download the entire file.
Megatools are reasonably simple and cleanly written. You can skim the entire code in an afternoon and see what it does. You can be completely in control of the update process for megatools. Pace of development is slow and changes are easy to review. This is all important if you value your security, as shown by issues with browser based solutions (mega.nz browser extension hacked). Megatools was written to avoid such issues.
Issue:
There are currently only 3 selections available on the Brave taskbar jump options (see supporting screenshots) and these are the Windows default jump options. The jump options that were previously available (e.g. New private window) are no longer available.
The reason this solution will not work for Brave (based on my further investigation) is because the Custom Destinations file (.customDestinations-ms) for Brave is missing (C:\Users%USERNAME%\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations).
There should be a Custom Destinations file in the above directory that matches the name of the directory for Brave found in the Implicit App Shortcuts folder (C:\Users%USERNAME%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\ImplicitAppShortcuts).
Now go to the extracted zip, open folder (for example AutomaticDestinations) and copy the files to the folder with the same name (AutomaticDestinations). Make sure you do this will all three folders. This worked for me in VM and on my PC.
Had similar problems recently with another chromium browser.
The fix for me was to drag an open webpage address onto the browser icon on the taskbar. (Pinning the website to the browser icon) The jump list, new window, new incognito window tasks as well as recent websites now show up with a right click. A potentially simpler fix ? (Let windows do the grunt).
Problem:
Multiple users around the world in different countries have incredible low download speeds, f.e. ISP Connection 120mbit, but MSFS2020 is downloading only with 1 to 20 mbit/s. The problem is there since release and is touching not only the download for the whole game or major updates, but also the ingame download through the marketplace.
Multiple users are reporting that at the same time, online speedtest and f.e Steam downloads have no problem and are giving the full download speed bandwith, so that it appears that its not a individual connection problem. Often the only thing which helps them is using a VPN and trying out different servers, sometimes even in the same country as they are located.
I managed to download the whole installation in about 2 hours with the max speed shown on some of the larger files at over 250MBps.
Subsequent updates all downloaded very quickly and in line with my expectations of a 300MBps connection.
The only thing which helps me is using a free VPN.
So for anyone who tried every step and is still suffering from download speeds like it is 2001 and doesnt want to pay for a VPN or give credit card informations:
1.) Google for ProtonVPN, register, download and install (absolutely no payment or credit card information is needed for the free servers from the USA, Nethlerlands and Japan
2.) Try every server from the USA, on Server 3, 4 and 8 I get at least 40 mbit, sometimes 70mbit (with a 120mbit connection), still not what I should get with my connection, but better than the 10mbit I get without VPN
I use Bell Fibe in NS with 1.5 Gbps service and have always suffered with slow downloads since the Tech Alpha. Max I get is 30Mbps until I connect a VPN. With a VPN connected, I can normally get 250-300Mbps.
The VPN connection also goes through your 2 routers, so its highly unlikely that its the 2 routers fault. Also basically everyone has slow download speed for msfs2020, the fault is on Asobo/Microsofts side.
Apart form the fact that I was getting good download speeds, then for a few months bad download speeds (maybe I messed up some settings) but now after making some adjustments to my network card settings and windows settings I am reliably getting close to my 300Mbps that my ISP provides.
I sent all my testing info through to Microsoft as a ticket. Most likely would only help those that are downloading from a specific server in Canada. Gave them everything I could so hopefully they use the data to trace things out.
I also suggested in my ticket to allow users to swap download endpoints from a list to allow users to potentially bypass hops that may be giving them issues. Much the same way we can change game servers, why not allow us to change download servers?
Recon's SOC recently responded to an attempted ransomware and extortion attack. It had all the markings of a nightmare scenario: malicious access through the VPN, an external server in the same IP block as the Colonial Pipeline incident, Cobalt Strike flying across the environment, and a system running an unauthorized copy of MEGAsync. We attributed the attack to a Ransomware-as-a-Service (RaaS) threat group, likely DarkSide, REvil, or their affiliates.
Through our initial response, we quickly identified and remediated compromised systems and accounts to contain the malicious activity. No files were encrypted. Our attention then turned toward an important question: what, if any, data was stolen? To answer this question, we turned to the MEGAsync logs. In this post, we'll outline our analysis of these logs so you know what to look for if you find yourself on the wrong side of an extortion attempt.
MEGA is a legitimate cloud backup service that has become a favorite for RaaS threat groups. Their MEGAsync software works how you would expect it: you point it at folders and shared drives and it uploads those files up to the cloud. It installs like any other Windows application. Look for it installed in places like C:\Users\\AppData\Local\MEGAsync\MEGAsync.exe and C:\ProgramData\MEGAsync\MEGAsync.exe.
MEGAsync's logs are stored in a "logs" folder in the same location as the MEGAsync.exe binary. With the exception of the most recent active log file, the older logs are compressed using gzip. You can decompress the logs using gunzip (gunzip -S .log *) or search them as-is using zcat -f and zgrep.
However, this only gives us the filenames, not the full folder path and drives that those files came from. We can identify the full file locations by reading the "Async open finished" events. We believe these events are recorded as the files are queued but are not yet uploaded. These entries are important because they show the specific systems, folders, and files that the attacker targeted.
Just because a file was queued, does not mean the upload was successful. In our case, many files failed to upload after we severed the system's network connection. We can identify these failed uploads by searching the logs for "(UPLOAD) finished with error"
An interesting entry appears if you search for "email" or "emails." Though we could not confirm it, the entry appears to reveal the yandex.ru email account that the attacker used to authenticate with MEGA.
Examining the MEGA logs is a useful for investigating data theft and and extortion incidents. If your organization does not have a legitimate business case for MEGA software, consider blocking it. Configure EDR tools to detect or prevent its use. Set up network controls to block connections to its associated domains, such as mega.co.nz, mega.io, and mega.nz.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription__stripe_mid1 yearThis cookie is set by Stripe payment gateway. This cookie is used to enable payment on the website without storing any patment information on a server.__stripe_sid30 minutesThis cookie is set by Stripe payment gateway. This cookie is used to enable payment on the website without storing any patment information on a server.Affiliate ID3 monthsAffiliate ID cookiecookielawinfo-checbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".cookielawinfo-checbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".cookielawinfo-checbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".Data 13 monthsData 23 monthsData 2JSESSIONIDsessionUsed by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests.PHPSESSIDsessionThis cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.woocommerce_cart_hashsessionThis cookie is set by WooCommerce. The cookie helps WooCommerce determine when cart contents/data changes.XSRF-TOKENsessionThe cookie is set by Wix website building platform on Wix website. The cookie is used for security purposes.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription__lc_cid2 yearsThis is an essential cookie for the website live chat box to function properly.__lc_cst2 yearsThis cookie is used for the website live chat box to function properly.__lc2_cid2 yearsThis cookie is used to enable the website live chat-box function. It is used to reconnect the customer with the last agent with whom the customer had chatted.__lc2_cst2 yearsThis cookie is necessary to enable the website live chat-box function. It is used to distinguish different users using live chat at different times that is to reconnect the last agent with whom the customer had chatted.__oauth_redirect_detectorThis cookie is used to recognize the visitors using live chat at different times inorder to optimize the chat-box functionality.Affiliate ID3 monthsAffiliate ID cookieData 13 monthsData 23 monthsData 2pll_language1 yearThis cookie is set by Polylang plugin for WordPress powered websites. The cookie stores the language code of the last browsed page.