mudmanc4

Moderators
  • Content count

    14,357
  • Joined

  • Last visited

  • Speed Test

    My Results

5 Followers

About mudmanc4

  • Rank
    TMN Seasoned Veteran
  • Birthday January 01

Contact Methods

  • AIM mudmanc4
  • MSN mudmanc4
  • Website URL http://lime-it.us
  • ICQ 330539369
  • Yahoo mudmanc4
  • Skype mudmanc4

Profile Information

  • Gender Male
  • Location In The Plex

Recent Profile Visitors

70,285 profile views
  1. Avast 11.2.2262 network probing

    It has been confirmed, that (at the least the latest version, others unknown at this time) the Avast network section will probe, at regular intervals, random ports and random known pages (existing on the network or not) for 'known' past threats or infiltrations. Firewall logs will reflect these probes, and block them as a threat, just as any proper firewall would detect and halt such network probes.
  2. It's not so good

    Here is the data for Shaw Communication at testmy.net http://testmy.net/host-history/shaw_communications Here is the data for Telus at testmy.net http://testmy.net/host-history/telus_communications Complete Data for Telus at testmy.net You can find charts for each provider, by going to 'Database Lookup' You can also search many variables between providers, rank, end user or member rank.
  3. Very nice glimpse into the global fiber optic submarine networking cable. Source A couple of example cables:  Below is a "deep cable"; where the tiny colored fibers are the trans global fiber network, same as above, without the shallow sea armor.    
  4. Do I need to keep browser open?

    Hi Sheila, Yes exactly. Many people simply reduce the window or open a new tab, or new browser window while the auto test is running. Once you close the window, or tab the test is running in , the test will be terminated.
  5. And you laugh at my tin foil hat XD

    True, until it's used for something other than what it was intended for. Pretty much just as everything else we know of has been
  6. Democratizing Webcam Eye Tracking on the Browser: WebGazer.js is an eye tracking library that uses common webcams to infer the eye-gaze locations of web visitors on a page in real time. The eye tracking model it contains self-calibrates by watching web visitors interact with the web page and trains a mapping between the features of the eye and positions on the screen. WebGazer.js was built It is written entirely in JavaScript and with only a few lines of code can be integrated in any website that wishes to better understand their visitors and transform their user experience. WebGazer.js runs entirely in the client browser, so no video data needs to be sent to a server. Source Now you understand why that sticky note hangs over my cam on the laptop. Though, this is not new technology, just getting a bit more ingrained in daily life.
  7.  FBI officials are warning private industry partners to be on the lookout for highly stealthy keystroke loggers that surreptitiously sniff passwords and other input typed into wireless keyboards. The FBI's Private Industry Notification is dated April 29, more than 15 months after whitehat hacker Samy Kamkar released a KeySweeper, a proof-of-concept attack platform that covertly logged and decrypted keystrokes from many Microsoft-branded wireless keyboards and transmitted the data over cellular networks. To lower the chances that the sniffing device might be discovered by a target, Kamkar designed it to look almost identical to USB phone chargers that are nearly ubiquitous in homes and offices. "If placed strategically in an office or other location where individuals might use wireless devices, a malicious cyber actor could potentially harvest personally identifiable information, intellectual property, trade secrets, passwords, or other sensitive information," FBI officials wrote in last month's advisory. "Since the data is intercepted prior to reaching the CPU, security managers may not have insight into how sensitive information is being stolen." It's not clear why the FBI waited so long to warn private industry players of the KeySweeper threat. The notification, which says the information was obtained through an undescribed "investigation," makes no mention of malicious sniffers being found in the wild. Kamkar told Ars that he hasn't heard of any reports of real attacks using devices similar to KeySweeper but that he couldn't rule out the possibility, either. Microsoft officials have pointed out that sniffing attacks work against any wireless device that doesn't use strong cryptography to encrypt the data transmitted between a keyboard and the computer it's connected to. The officials have said that company-branded keyboards manufactured after 2011 are protected because they use the Advanced Encryption Standard. Bluetooth-enabled wireless keyboards are also protected. Anyone using a wireless keyboard from Microsoft or any other maker should ensure it's using strong cryptography to prevent nearby devices from eavesdropping on the radio signal and logging keystrokes. Source This is interesting in several ways, first, this has been happening on peripherals for ages. Secondly, why the OMG FBI warning you say? That means it's an old issue that has been exploited to it maximum usability, and there are many other means to accomplish the very same thing. imo of course.
  8. sharing

    What type of file will they accept?
  9. MossyMan

    I feel you MossyMan, we've all been there. Hang tough!
  10. sharing

    What cache ;
  11. Anyone using Avast 'network security' who can give me a few answers? Seems there are people saying the program is probing specific ports and pages that would never exist in any end user machine.
  12. New rules that affect open source firmware on Wi-Fi routers will be implemented on June 2 but not all network hardware will prevent the loading of third-party software. Linksys has been collaborating with chipmaker Marvell and the makers of OpenWrt to make sure its latest WRT routers can comply with the new rules without blocking open source firmware, company officials told Ars. Linksys’s effort stands in contrast with TP-Link, which said it would entirely prevent loading of open source firmware on its routers to satisfy the new Federal Communications Commission requirements. Blocking third-party firmware is the easiest way to comply with the FCC rules, which aim to limit interference with other devices by preventing user modifications that cause radios to operate outside their licensed RF (radio frequency) parameters. The FCC wrote its rules in response to interference with FAA Doppler weather radar systems. Routers using certain portions of the 5GHz band were already required to use dynamic frequency selection (DFS) in order to detect nearby radar systems and avoid operating on the same channel. But it’s possible for users to disable dynamic frequency selection—the FCC hascalled this a “major cause of harmful interference.” Most cases of interference have been caused either by disabling DFS or “devices that have been modified to operate in frequency bands in which they are not certified to operate,” the FCC says. “Our responsibility to the open source community” Any 5GHz routers sold on or after June 2 must include security measures that prevent these types of changes. But router makers can still allow loading of open source firmware as long as they also deploy controls that prevent devices from operating outside their allowed frequencies, types of modulation, power levels, and so on. This takes more work than simply locking out third-party firmware entirely, but Linksys, a division of Belkin, made the extra effort. On and after June 2, newly sold Linksys WRT routers will store RF parameter data in a separate memory location in order to secure it from the firmware, the company says. That will allow users to keep loading open source firmware the same way they do now. Other Linksys routers, such as Max-Stream devices, will block open source firmware. But continuing support on the WRT line is a natural move for Linksys, given that the OpenWrt and DD-WRT third-party firmware was originally built for the company’s WRT54G routers more than a decade ago. “They're named WRT… it's almost our responsibility to the open source community,” Linksys router product manager Vince La Duca told Ars. FCC: Open source router software is still legal—under certain conditions Locking out OpenWRT and DD-WRT is the easiest way to comply with new FCC rules. WRT stands for “Wireless RouTer,” and Linksys has stuck with its naming conventions and support for open source for many years. The “WRT54GL” released in 2005 offered speeds of up to 54Mbps. The “L” stood for Linux. Linksys resurrected the classic blue and black design of the WRT in 2014 with the new WRT1900AC. The numbers and letters indicated support for up to 1900Mbps and the 802.11ac Wi-Fi standard. That router as well as the newer WRT1900ACS and WRT1200AC will continue to support open source firmware after the new rules take effect, La Duca said. "The hardware design of the WRT platform allows us to isolate the RF parameter data and secure it outside of the host firmware separately," Linksys said in a written statement given to Ars. La Duca declined to get more specific about Linksys's exact method. Even though this is about enabling open source, Linksys’s method is proprietary and provides a competitive advantage over other router makers that aren’t supporting open source, La Duca said. Using open source isn't about breaking the rules While Linksys’s support of open source is partly a marketing strategy, La Duca understands why customers want to use OpenWrt and similar software. “The real benefit of open source is not breaking the rules and doing something with malicious intent, the value of open source is being able to customize your router, to be able to do privacy browsing through Tor, being able to build an OpenVPN client, being able to strip down the firmware to do super lean, low-latency gaming,” La Duca said. “It's not about ‘I'm going to go get OpenWrt to go and piss off the FCC.' It's about what you can do in expanding the capabilities of what we ship with.” But that doesn’t extend across all Linksys routers. For Max-Stream devices and other routers that lack WRT branding, “open source is not a value proposition that we are promoting,” La Duca said. For those non-WRT platforms, Linksys is not working with chip providers to enable open source support. "All Linksys legacy and Max-Stream routers will have the full host firmware locked down," the Linksys statement said. The company noted that these routers were never marketed to open source users as the WRT routers are. Whether open or closed, Linksys said all of its dual- and tri-band routers will comply with the new FCC rules "that require our routers and software to be secured to prevent changing the power output or unauthorized channel selection of the router on the 5Ghz band." (There are also similar new requirements implemented by the European Telecommunications Standards Institute, Linksys said.) “No one else was prepared for this” Imre Kaloz, a key OpenWrt developer, told Ars that he isn't aware of any other vendors making a similar effort to support open source. Kaloz has tried to get other hardware makers interested, but he said his attempts have so far only earned him some marketing e-mails. Still, Kaloz holds out hope that other vendors will see the work Linksys has done and try to copy it. “It's not that complicated, it's simply that no one else was prepared for this,” Kaloz said. Most of the necessary changes happened on the hardware side, Kaloz said. But OpenWrt developers also worked closely with Marvell to update the open source wireless driver so that OpenWrt can continue to work, he said. Default OpenWrt functionality will remain unchanged on Linksys WRT routers, Kaloz said. It’s open source and can thus be modified, but by default OpenWrt doesn’t let users do anything that would violate FCC rules, he said. DD-WRT, which is based on OpenWrt, is capable of disabling DFS. Although Linksys has proven that open source firmware can still be used under the new FCC rules, it’s clear that options for open source users will be more limited than they are today. Kaloz wishes the FCC had taken a different approach, one focused on punishing people who cause interference without preventing legitimate uses of network hardware. The decisions, he said, "have been made by lawyers who had not too much technical knowledge." Source
  13. t_dclnt.fxp is not an object file

    Try using windows excel to view those files.
  14. Upload speed inconsistency

    @Diffusion Fermont I do notice you are using more than one IP to access testmy.net If your at the same location, and getting different IP assigned, there are possibilities that one of the IP's you had before signing up to log results,was used by someone with a different Internet package. Are you testing from work or something, and then at home as well?