This page will contain images about emule, as they become available.EMuleIn computing, eMule is a peer to peer file sharing application that works with both eDonkey and Kad Network and has more features than the eDonkey client. eMule is open source software released under the GNU General Public License. eMule runs on Microsoft Windows; however, its codebase forms the basis for a Linux client, xMule, and a multiplatform client, aMule. The distinguishing features of eMule are the direct exchange of sources between client nodes, fast recovery of corrupted downloads, and the use of a credit system to reward frequent uploaders. Furthermore eMule transmits data in (Zlib-)compressed form to save bandwidth. Another feature of eMule is the ability to accept "ed2k" links from a web browser and begin downloading the file(s) these links refer to. These links ensure that the file being downloaded shares the same hash, and therefore is not a "fake". Recently, many of the sites which provide these links have been taken offline by authorities due to accusations of copyright infringement, as well as a questionable legality of the links they provide. Matching file sources is verified through the use of the MD4 algorithm. eMule is coded in Visual C++ .NET using the Microsoft Foundation Classes and because it is a popular open-source program, hundreds of eMule mods (modifications of the original eMule) have appeared on the Internet. HistoryThe eMule project was started on May 13, 2002 by Hendrik Breitkreuz (a.k.a. Merkur) who was dissatisfied by the original eDonkey2000 client. Over time 7 more developers joined the effort. The source was first released at version 0.02 and it was published on SourceForge on July 6, 2002. It was first released as a binary on August 4, 2002 at version 0.05a. The "Credit System" was implemented for the first time on September 14, 2002 in version 0.19a. The eMule project website started up on December 8, 2003. Since its inception, eMule has been downloaded by over 85 million people. Currently the project is staffed by 16 people: 2 developers, 2 project managers (including the founder Breitkreuz), 3 testers, 9 debug testers. The official web site is supported by 7 web developers and 4 moderators. Recent eventsRecent versions (v0.40+) of eMule have added support for the Kad Network. This network has an implementation of the Kademlia protocol, which does not rely on central servers as the eDonkey network does. Also added in recent versions were "Unicode Search" (allowing for searches for files in non-Latin alphabets) and the ability (not supported in Kad Network) to search servers for files with complete sources of unfinished files. In new versions, a "Bad source list" was added. The application adds an IP address to this list after one unsuccessful connection. After adding an IP to the "Bad source list", the application treats this IP as a "dead" IP. Unavailable IPs are banned for a time period from 15 to 45 minutes. Some users have complained that it leads to a loss of active sources and subsequently slows download speed. Other recent additions include: the ability to run eMule from a user account with limited privileges (thus enhancing security), and intelligent corruption handling (so that a corrupted chunk, 9.28 MB in size, does not need to be re-downloaded entirely). The 0.46b version added the creation and management of "collection" files, which contain a set of links to files intended to be downloaded as a set. eMule is now considered a stable product, and new versions are not released as often as they used to be - 2 to 3 months is now a typical time interval between releases. It is recommended to change the default ports of eMule to higher numbers (for example 20000 instead of 4662), because recently many ISPs are throttling default P2P ports resulting in slow performance. Network and file sharing issuesBasic conceptsFile identificationAll files are given a hash value that depends on the file's contents, but not its filename. This allows each user to find all sources to a particular file no matter what file name each user has given the file. Files are broken into "chunks" of 9.28 MB each (the last chunk may be smaller if the file size is not exactly divisible by the chunk size). A file's hash value is computed by first computing the MD4 checksum of each chunk, and then computing the MD4 checksum of the string of those chunks' checksums concatenated with each other. Identifying other clientsLike the file hash, each user in the network gets a unique and permanent user hash. This user identification is highly secured by a public / private key handshake to prevent misuse. Downloading dataAfter determining sources for a file (i.e. other clients who are sharing that file), a client contacts each of those sources to request the file. Each client maintains a "download queue" of other clients who are requesting files for download. Once a client reaches the top of such a queue, the clients contact each other and transfer begins. Clients usually request the chunk that fewest other sources have to aid distribution of the file through the network; otherwise rare chunks may generate a bottleneck. If a client already has most of a chunk, however, it may choose to request the rest of that chunk first because only complete chunks can be shared. CompressionBefore sending data eMule attempts to compress the data with [zlib] set at maximum compression. Then it chooses the smaller set of data to transmit. For already compressed files this is likely to be the raw file, while uncompressed files are likely to result in zlib compressed data to be transmitted. Classic server based eD2k(eD2k :EDonkey network) Connecting to the networkThe key to this network is the eD2k server. Each client must be connected to a server to enter the network. When connecting your client to a server, the server checks to see if other clients can freely connect to your client. If yes, the server assigns your client a so-called high ID. If communication is blocked, the server assigns your client a low ID. After the ID is assigned, eMule will send a list of all shared files to the server. The server adds the filenames and hash values you sent to its database. Searching for filesOnce connected to the network, the client can search for keywords in filenames. A search can either be local or global. If it’s a local search (searches only the server you are connected to), searches are quicker but will have fewer results. If the search is a global search (searches all the servers within the network), it will take longer but have more results. Each server looks up the keyword in its local database and returns any file names (with the hash value) that matches the keyword. Note that there are fake servers in the network that do not return any results for certain type of searches (e.g. mp3 files) Finding sources for filesDownloads can be added by eMule’s search function or a special eD2k link format offered on many websites. Once they are in the Download list, eMule first queries the local (connected) server then all other servers in the network for sources to that particular download. The server looks up the file’s hash value in its database and returns the clients it knows for having it. Sources are other clients who have at least downloaded one entire part (9.28 MB) of the file matching the hash. Kad serverless network(based on Kademlia protocol) Connecting to the networkThe only thing needed to connect to this network is the IP and port of any eMule client already connected. This is called a Boot Strap. Once a client is in the network, the client then requests for other clients to determine if it can be contacted freely. This process is very similar to the HighID/LowID check on the servers. If you can be freely contacted, you are assigned an ID (similar to a HighID) and given an open status. If you are not freely contacted, you are given a firewalled status. From version v.44a on, the Kad network supports a Buddy for firewalled users. Buddies are other Kad clients who have status open and work as a relay for connections, that the firewalled user cannot manage. Searching in KadIn this network it does not matter what you search for. Be it a search for filenames, for sources of a download or for other users, all work pretty much the same. There are no servers to keep track of clients and the files they share so it has to be done by each participating client in the network – in essence, every client is also a small server. Since every client is identified by a unique hash value, the idea of Kademlia is to associate a certain “responsibility” based on this hash. Each client in the Kad network works as a server for certain keywords or sources. The clients hash determines the specific keywords or sources. So the goal of any kind of search is to find those clients that have the responsibility for the current search topic. This is accomplished by a complex calculation of the possible distance to the target client by asking other clients for the shortest route to it. Basic rules of communication behavioreMule and other programs on eDonkey network support the network in two basic ways: 1) Users are forced to share files: Shared files larger than 9500 KB are divided and downloaded in parts, so that a recipient starts to share the parts of the file already downloaded even before the download of the whole file is complete. The recipient is forced to share in this way until the download is complete. 2) Users are forced to share their bandwidth, thus increasing network's data stream: The official version of eMule forces the users to set their maximum download speed to no more than four times their maximum upload speed. This limitation does not apply if the maximum upload speed is set to 10K per second or more. Although there are many mods of eMule, it is hard to find one that doesn't enforce the second feature, which is a part of official eMule policy. Furthermore, attempting to circumvent the uploading feature can possibly slow a user's download, as he will get worse credits from uploaders. Also, many known "leecher" clients are often banned from the downloading through various means by eMule's mods (banning is not supported in official version). eMule includes a feature that limits download and upload speeds, so that they do not exceed the limits set by the user. eMule versions before 0.47a cannot share files larger than about 4 GB. This was an inherent limitation of the ed2k protocol. With the release of 0.47a, this limit was raised to 256GB, but only for clients supporting it (currently just eMule and aMule). SummaryBoth networks have totally different concepts for achieving the same: Searching for files and finding sources to a file. The main goal of the Kad network is to be independent of servers and improve scalability. Servers can only handle a certain amount of users and should a large server go down the network is severely handicapped. Kad network is self-organising and tunes itself for best possible performance depending on the number of users and their connection qualities. Therefore, it is more resistant to a large-scale network loss. Some servers also limit the number of files that can be shared by any particular user. This limitation doesn't exist in Kad network, therefore this network is more suitable for users that share big collections of files. eMule modsAs a popular open source program, eMule has many variants, usually called mods. Some mods started as a fork of a eMule code, and then continued to develop independently of the official version. A popular mod of this type is eMule Plus. It does not have Kademlia protocol implemented, but proponents of this mod credit it for a better GUI and an ability to achieve better download speeds than the official version. Other mods follow official eMule releases, and make their own releases based on each new release of the official version. Often features first debuted in a mod later find their way into the official version. Credit systemIntroductionThe credit system is used to reward users contributing to the network, i.e. uploading to other clients. The strict queue system in eMule is based on the waiting time a user has spent in the queue. The credit system provides a major modifier to this waiting time by taking the upload and download between the two clients into consideration. The more a user uploads to a client the faster he advances in this client's queue. The modifiers are calculated from the amount of transferred data between the two clients. The values used can be seen in the client's details dialog. To view this information, right click on any user and choose View Details. Credit calculationA user's position in other clients' queues depends on various factors, including the time they have been waiting in the queue, the upload priority for the requested file, and the user's credit. These factors are all expressed in an integer value, and their total gives a "score" which is used to rank the users in the queue. The credit is calculated in the following way:
Notes
Colors of the Progress BarEach download in the Transfers tab has a coloured bar to show current file availability and progress. Basic Styles(flat style) (shaded style) Black shows the parts of the file you already have. Red indicates a part missing in all known sources. Different shades of blue represent the availability of this part in the sources. The darker the blue, the more sources have this part. Yellow denotes a part being downloaded. The green bar on top shows the total download progress of this file (flat style) (shaded style) A green bar stands for a completed download. (flat style) (shaded style) A dark red or blue progress bar denotes a stopped or paused download. Download BarIf you expand the download you see each of its sources with their corresponding bar. To see the sources just double-click a download (or single click, depends on the settings in Options -> Display ). Here the colours have a slightly different meaning: (flat style) (shaded style) Black indicates parts you already have Blue are parts you still need for this download Silver stands for parts this source is also missing Green parts are currently downloading Yellow denotes a pending (already requested) part Source CountThe four values xx/yy+aa (zz) displayed after the progress bar is the source count for this file and shows following information. • xx - Number of useful sources • yy - Total number of sources • + aa - Number of Asked for another file sources (only shown when Advanced Controls is enabled) • zz - Currently transferring sources excellent Obtained PartsThis bar appears in the upload queue if supported by the other client. It shows the progress of the file this user is downloading. Black are parts this user has already completed Silver ones are parts still missing Green parts are currently uploading Yellow denotes a pending (already requested) part Availability of shared filesEach shared file shows its availability in the form of a bar. The color coding is similar to the one used with the progress bar Red indicates a part missing in all known sources Different shades of blue give an idea how well-spread different parts are Network status(data for eDonkey network)
This page about emule includes information from a Wikipedia article. Additional articles about emule News stories about emule External links for emule Videos for emule Wikis about emule Discussion Groups about emule Blogs about emule Images of emule |
|
(data for eDonkey network). They also sponsor the following teams:. Different shades of blue give an idea how well-spread different parts are. In addition to the venues in Philadelphia and Wilkes-Barre, Pennsylvania, Wachovia also sponsors an annual PGA tournament in Charlotte, called the Wachovia Championship. Red indicates a part missing in all known sources. Interestingly, Capital One was originally established as the credit card division of Signet Bank, which was later purchased by First Union prior to the Wachovia merger. The color coding is similar to the one used with the progress bar. This purchase would give Wachovia an established credit card division, plus allow it to establish (via Capital One's purchase of Hibernia National Bank) a banking presence in Louisiana and strengthen its presence in Texas. Each shared file shows its availability in the form of a bar. Nevertheless, speculation remains that Wachovia may buy Capital One. Yellow denotes a pending (already requested) part. As of 2006, new credit card accounts opened through Wachovia will remain with this new division. Green parts are currently uploading. On November 2, 2005 Wachovia announced that it would end its credit card relationship with MBNA and start up its own credit card division. Silver ones are parts still missing. The payment is part of the agreement Wachovia predecessor First Union made in 2000 when it sold its credit card portfolio to MBNA. Black are parts this user has already completed. Multiple sources have reported that as part of its agreement with Wachovia, MBNA is required to pay the nine-figure sum if it ever sells to Wachovia's cross-town rival Bank of America. It shows the progress of the file this user is downloading. Wachovia is set to get $100 million out of this deal. This bar appears in the upload queue if supported by the other client. Within a week of the deal's collapse, MBNA entered into an agreement to be purchased by Wachovia's chief rival, Bank of America. • zz - Currently transferring sources excellent. However, the deal fell through when Wachovia balked at MBNA's purchase price. • + aa - Number of Asked for another file sources (only shown when Advanced Controls is enabled). In June of 2005, Wachovia negotiated to purchase monoline credit card company MBNA. • yy - Total number of sources. This purchase will give Wachovia 19 branches in Southern California, but more importantly, will more than double the size of Wachovia's dealer financial services business, making it the nation's ninth largest auto loan originator. • xx - Number of useful sources. Wachovia will enter the California market with its purchase of Western Financial Bank. The four values xx/yy+aa (zz) displayed after the progress bar is the source count for this file and shows following information. The merger created the largest bank in the southeast, the fourth largest bank in the United States in terms of holdings, and the second largest in terms of number of branches. Yellow denotes a pending (already requested) part. On November 1, 2004, Wachovia completed the acquisition of banking competitor SouthTrust Corporation, a transaction valued at $14.3 billion. Green parts are currently downloading. It also operates Wachovia Securities, its brokerage services subsidiary. Silver stands for parts this source is also missing. It has banking centers in 15 East coast states and Washington, D.C. Blue are parts you still need for this download. Wachovia is currently ranked number 23 on the Forbes 500 list for 2003, and is the fourth largest bank holding company in the US. Black indicates parts you already have. Formerly known as the First Union Center and the First Union Spectrum (both Philadelphia) and First Union Arena (Wilkes-Barre), they are now known as the Wachovia Center, Wachovia Spectrum, and Wachovia Arena. (shaded style). The merger also affected the names of the indoor professional sports arenas in Philadelphia and Wilkes-Barre, Pennsylvania. (flat style). Charlotte, North Carolina's One, Two, Three, and Four First Union buildings became One, Two, Three, and Four, Wachovia Center (respectively), and the 55-story First Union Tower in downtown Miami became the Wachovia Tower. Here the colours have a slightly different meaning:. When Wachovia and First Union merged, the multiple skyscrapers with First Union's name came under Wachovia's name. To see the sources just double-click a download (or single click, depends on the settings in Options -> Display ). The company has also been reporting record revenues since the merger. If you expand the download you see each of its sources with their corresponding bar. In addition, the company's stock price has remained strong, and provided a good return to legacy Wachovia shareholders, in contrast to SunTrust's claims during the takeover attempt. A dark red or blue progress bar denotes a stopped or paused download. In fact, Wachovia has been ranked number one in customer satisfaction every year since the merger. (shaded style). The company's slow strategy to combine seems to have prevented large customer attrition rates. (flat style). In comparison the CoreStates purchase, the merger of First Union and Wachovia has been a huge success. A green bar stands for a completed download. This process officially ended on August 18, 2003, almost 2 years after the merger took place. (shaded style). The company first began converting systems in the Southeast United States (where both banks had branches) before moving to the Northeast, where First Union branches only had to change their signs to reflect the new company name and logo. (flat style). Over a period of several years, legacy Wachovia computer systems were converted to First Union systems. The green bar on top shows the total download progress of this file. In order to prevent a repeat of the CoreStates fiasco, the new Wachovia took a deliberately long period of time to combine the banking operations of the new company. Yellow denotes a part being downloaded. On September 4, 2001, First Union and Wachovia officially merged to form the new Wachovia Corporation. The darker the blue, the more sources have this part. Wachovia paid Bank One a $350 million termination fee. Different shades of blue represent the availability of this part in the sources. After entering into negotiations, the new Wachovia agreed to buy back its portfolio from Bank One in September of 2001 and resell it to MBNA. Red indicates a part missing in all known sources. First Union sold their credit card portfolio to MBNA in August of 2000. Black shows the parts of the file you already have. The cards, which would have still been branded as Wachovia, would have been issued through Bank One's First USA division. (shaded style). In April of 2001, Wachovia agreed to sell its $8 billon credit card portfolio to Bank One. (flat style). Another problem concerned each banks' credit card divisions. Each download in the Transfers tab has a coloured bar to show current file availability and progress. They rejected SunTrust's attempts to elect a new Board of Directors for Wachovia, and thus, ended SunTrust's hostile takeover. The credit is calculated in the following way:. On August 3, 2001, Wachovia shareholders approved the First Union deal. These factors are all expressed in an integer value, and their total gives a "score" which is used to rank the users in the queue. Long a rumored suitor for Wachovia, SunTrust had been in on-again off-again merger talks with it over the course of many years, with both Wachovia and SunTrust eventually confirming the most recent effort took place during the winter of 2000 before Wachovia terminated the discussions. A user's position in other clients' queues depends on various factors, including the time they have been waiting in the queue, the upload priority for the requested file, and the user's credit. In its effort to make the "Smoke-and-Coke" deal appeal to investors, SunTrust argued that it would provide a smoother transition than First Union and offered a higher cash price for Wachovia stock than First Union. To view this information, right click on any user and choose View Details. On May 14, 2001, Atlanta-based SunTrust announced a rival takeover bid for Wachovia, the first hostile takeover attempt in the banking sector in many years. The values used can be seen in the client's details dialog. First Union responded to these concerns by placing the wealth management and Carolinas-region headquarters in Winston-Salem. The modifiers are calculated from the amount of transferred data between the two clients. The city of Winston-Salem was concerned both by job losses by the move and the loss of stature from losing a corporation. The more a user uploads to a client the faster he advances in this client's queue. Citizens and politicians of Winston-Salem suffered from a hurt of their civic pride because the city would lose Wachovia's corporate headquarters to Charlotte, partly because Winston-Salem is a much smaller city than Charlotte. The credit system provides a major modifier to this waiting time by taking the upload and download between the two clients into consideration. Analysts were concerned of First Union's ability to merge with another large company because of the CoreStates deal. The strict queue system in eMule is based on the waiting time a user has spent in the queue. The deal was met with criticism and doubt by several groups. uploading to other clients. At the same time, Wachovia's name and corporate identity would survive, an important source of pride to Wachovia's board. The credit system is used to reward users contributing to the network, i.e. Analysts said this move was most likely to help First Union acquire a new identity, as Wachovia's reputation was far better with consumers than First Union. Often features first debuted in a mod later find their way into the official version. As an important part of the deal, First Union would shed its name and assumed the Wachovia identity and stock ticker. Other mods follow official eMule releases, and make their own releases based on each new release of the official version. The former CEO of Wachovia, Bud Baker, later said that he and First Union's CEO, Ken Thompson, met at interstate motels to keep their talks of merger as secret as possible. It does not have Kademlia protocol implemented, but proponents of this mod credit it for a better GUI and an ability to achieve better download speeds than the official version. While Wachovia had been viewed as an acquisition candidate after running into problems with earnings and credit quality in 2000, the suitor shocked analysts as most assumed that should Wachovia be sold it would be to SunTrust in the long-assumed "Smoke-and-Coke" merger (the nickname coming from Wachovia's long relationship with tobacco companies and SunTrust's holdings of Coke stock dating from Coke's initial public offering). A popular mod of this type is eMule Plus. This was viewed with great surprise by the financial press and security analysts. Some mods started as a fork of a eMule code, and then continued to develop independently of the official version. Although the merger was billed in the proxy as a merger of equals by pooling, the deal was actually a purchase of Wachovia by First Union. As a popular open source program, eMule has many variants, usually called mods. On April 16, 2001, Charlotte-based First Union Corporation announced it would merge with Winston-Salem-based Wachovia Corporation. This limitation doesn't exist in Kad network, therefore this network is more suitable for users that share big collections of files. This is very ironic since the company weasled the judge into believing that the legitimate owner had no interest in the domain name, but Wachovia did. Some servers also limit the number of files that can be shared by any particular user. As of this writing, the domain name is owned by Wachovia, but is not being used. Therefore, it is more resistant to a large-scale network loss. Recently, Wachovia has sued for and obtained several domain names of sites warning people about Wachovia, including wachovia-sucks.com. Kad network is self-organising and tunes itself for best possible performance depending on the number of users and their connection qualities. However, the company has taken steps to silence anyone who gives an honest opinion of the bank. Servers can only handle a certain amount of users and should a large server go down the network is severely handicapped. First Union, now Wachovia, has proceeded to trash the Wachovia named. The main goal of the Kad network is to be independent of servers and improve scalability. This tactic is similiar to ValueJet renaming itself after it killed a plane full of passengers to make an extra buck by carying volatile materials. Both networks have totally different concepts for achieving the same: Searching for files and finding sources to a file. Unfortunately for First Union's customers, the bank itself had not change. With the release of 0.47a, this limit was raised to 256GB, but only for clients supporting it (currently just eMule and aMule). First Union found a far small bank that had a good reputation, and proceeded to purchase it in order to cover up its past. This was an inherent limitation of the ed2k protocol. The reputation was so bad that the company felt that it had to abandon its brand name and acquire a new one. eMule versions before 0.47a cannot share files larger than about 4 GB. First Union had a terrible reputation for incompetence and fraud. eMule includes a feature that limits download and upload speeds, so that they do not exceed the limits set by the user. In 2000, legacy Wachovia made its final purchase, which was Republic Security Bank, giving its first entry into Florida. Also, many known "leecher" clients are often banned from the downloading through various means by eMule's mods (banning is not supported in official version). In 1998, legacy Wachovia acquired two Virginia-based banks, Jefferson National Bank and Central Fidelity Bank. Furthermore, attempting to circumvent the uploading feature can possibly slow a user's download, as he will get worse credits from uploaders. This purchase made legacy Wachovia one of the few companies with dual headquarters: one in Winston-Salem and one in Atlanta. Although there are many mods of eMule, it is hard to find one that doesn't enforce the second feature, which is a part of official eMule policy. Founded as Atlanta National Bank on September 14, 1865, and later renamed to First National Bank of Atlanta, this institution was the oldest national bank in Atlanta. This limitation does not apply if the maximum upload speed is set to 10K per second or more. On December 12, 1986 Wachovia took over First Atlanta. 2) Users are forced to share their bandwidth, thus increasing network's data stream: The official version of eMule forces the users to set their maximum download speed to no more than four times their maximum upload speed. Wachovia Bank and Trust was formed in 1911 by the merger of Wachovia National Bank (founded 1879) and Wachovia Loan and Trust (founded 1893), and was located in Winston-Salem, North Carolina. The recipient is forced to share in this way until the download is complete. First Union had to restructure and lay off thousands of employees in 1999, partly as a result of the purchase of CoreStates. 1) Users are forced to share files: Shared files larger than 9500 KB are divided and downloaded in parts, so that a recipient starts to share the parts of the file already downloaded even before the download of the whole file is complete. Partly due to the CoreStates purchase and partially due to 80 other bank purchases over the last few years, First Union experienced several years of lower earnings and no dividend growth. eMule and other programs on eDonkey network support the network in two basic ways:. Furthermore, First Union substanially overpaid for CoreStates at over 4 times book value. This is accomplished by a complex calculation of the possible distance to the target client by asking other clients for the shortest route to it. As a result, customers left the bank in droves - First Union experienced a 19 percent attrition rate - because of poor customer service and the account issues. So the goal of any kind of search is to find those clients that have the responsibility for the current search topic. This attempt led to multiple problems: poorly trained employees (as CoreStates tellers were not familiar with the new systems) and First Union and CoreStates' systems unable to communicate with each other, which led to such problems as account access issues and payments not being correctly applied to loans. The clients hash determines the specific keywords or sources. To start with, First Union attempted to rapidly integrate CoreStates' systems into First Union. Each client in the Kad network works as a server for certain keywords or sources. The purchase proved to be a fiasco for a number of reasons. Since every client is identified by a unique hash value, the idea of Kademlia is to associate a certain “responsibility” based on this hash. CoreStates Financial Corporation, headquartered in Philadelphia, Pennsylvania, was acquired by First Union in April 1998. There are no servers to keep track of clients and the files they share so it has to be done by each participating client in the network – in essence, every client is also a small server. Over the decades, First Union purchased over 80 other banks before purchasing Wachovia, the majority of them in the 1990s. Be it a search for filenames, for sources of a download or for other users, all work pretty much the same. First Union National Bank of North Carolina was originally formed in 1958 with the merger of Union National Bank and First National Bank and Trust Company of Asheville. In this network it does not matter what you search for. It merged with Wachovia Corporation in 2001, and the combined company kept Wachovia's name. Buddies are other Kad clients who have status open and work as a relay for connections, that the firewalled user cannot manage. First Union Corporation was a large banking chain based in Charlotte, North Carolina. From version v.44a on, the Kad network supports a Buddy for firewalled users. First Union then took the Wachovia name. If you are not freely contacted, you are given a firewalled status. While the transaction was billed as a merger of equals, the transaction was actually a purchase of the legacy Wachovia by Charlotte-based First Union Corporation. If you can be freely contacted, you are assigned an ID (similar to a HighID) and given an open status. Today's Wachovia Corporation was created by the merger of the legacy Wachovia Corporation and First Union Corporation. This process is very similar to the HighID/LowID check on the servers. (See Old Salem.). Once a client is in the network, the client then requests for other clients to determine if it can be contacted freely. The area formerly known as Bethabara is now inside the city limits of Winston-Salem, North Carolina. This is called a Boot Strap. When Moravian settlers arrived in Bethabara, North Carolina in 1753, they gave this name to the land they acquired, because it resembled a valley along the Danube River called Die Wachau. The only thing needed to connect to this network is the IP and port of any eMule client already connected. The origin of the name is the Latin form of the German name Wachau. (based on Kademlia protocol). Wachovia, pronounced wah-KO-vee-yah, has one of the most unusual corporate names in the United States. Sources are other clients who have at least downloaded one entire part (9.28 MB) of the file matching the hash. . The server looks up the file’s hash value in its database and returns the clients it knows for having it. Wachovia Corporation NYSE: WB, based in Charlotte, North Carolina is one of the largest banking chains in the United States. Once they are in the Download list, eMule first queries the local (connected) server then all other servers in the network for sources to that particular download. Each server looks up the keyword in its local database and returns any file names (with the hash value) that matches the keyword. Philadelphia 76ers (NBA). If the search is a global search (searches all the servers within the network), it will take longer but have more results. Charlotte Bobcats (NBA). If it’s a local search (searches only the server you are connected to), searches are quicker but will have fewer results. Miami Dolphins (NFL). A search can either be local or global. New York Giants (NFL). Once connected to the network, the client can search for keywords in filenames. Wachovia named fourth WORST bank in the world. The server adds the filenames and hash values you sent to its database. 700,000 Bank Customers' Account Information Allegedly Stolen. After the ID is assigned, eMule will send a list of all shared files to the server. Scope of bank data theft grows to 676,000 customers. If communication is blocked, the server assigns your client a low ID. The theft affected nearly 50,000 Wachovia customers, and the bank knew it ... If yes, the server assigns your client a so-called high ID. More than 100,000 customers of Wachovia and Bank of America have been notified that their financial records may have been stolen. When connecting your client to a server, the server checks to see if other clients can freely connect to your client. Wachovia knew or should have known that customers' private information was being stolen or misappropriated. Each client must be connected to a server to enter the network. Wachovia lets hackers get access to bank accounts. The key to this network is the eD2k server. Bank security breach may be biggest yet. (eD2k :EDonkey network). For already compressed files this is likely to be the raw file, while uncompressed files are likely to result in zlib compressed data to be transmitted. Then it chooses the smaller set of data to transmit. Before sending data eMule attempts to compress the data with [zlib] set at maximum compression. If a client already has most of a chunk, however, it may choose to request the rest of that chunk first because only complete chunks can be shared. Clients usually request the chunk that fewest other sources have to aid distribution of the file through the network; otherwise rare chunks may generate a bottleneck. Once a client reaches the top of such a queue, the clients contact each other and transfer begins. Each client maintains a "download queue" of other clients who are requesting files for download. other clients who are sharing that file), a client contacts each of those sources to request the file. After determining sources for a file (i.e. This user identification is highly secured by a public / private key handshake to prevent misuse. Like the file hash, each user in the network gets a unique and permanent user hash. A file's hash value is computed by first computing the MD4 checksum of each chunk, and then computing the MD4 checksum of the string of those chunks' checksums concatenated with each other. Files are broken into "chunks" of 9.28 MB each (the last chunk may be smaller if the file size is not exactly divisible by the chunk size). This allows each user to find all sources to a particular file no matter what file name each user has given the file. All files are given a hash value that depends on the file's contents, but not its filename. It is recommended to change the default ports of eMule to higher numbers (for example 20000 instead of 4662), because recently many ISPs are throttling default P2P ports resulting in slow performance. eMule is now considered a stable product, and new versions are not released as often as they used to be - 2 to 3 months is now a typical time interval between releases. The 0.46b version added the creation and management of "collection" files, which contain a set of links to files intended to be downloaded as a set. Other recent additions include: the ability to run eMule from a user account with limited privileges (thus enhancing security), and intelligent corruption handling (so that a corrupted chunk, 9.28 MB in size, does not need to be re-downloaded entirely). Some users have complained that it leads to a loss of active sources and subsequently slows download speed. Unavailable IPs are banned for a time period from 15 to 45 minutes. After adding an IP to the "Bad source list", the application treats this IP as a "dead" IP. The application adds an IP address to this list after one unsuccessful connection. In new versions, a "Bad source list" was added. Also added in recent versions were "Unicode Search" (allowing for searches for files in non-Latin alphabets) and the ability (not supported in Kad Network) to search servers for files with complete sources of unfinished files. This network has an implementation of the Kademlia protocol, which does not rely on central servers as the eDonkey network does. Recent versions (v0.40+) of eMule have added support for the Kad Network. The official web site is supported by 7 web developers and 4 moderators. Currently the project is staffed by 16 people: 2 developers, 2 project managers (including the founder Breitkreuz), 3 testers, 9 debug testers. Since its inception, eMule has been downloaded by over 85 million people. The eMule project website started up on December 8, 2003. The "Credit System" was implemented for the first time on September 14, 2002 in version 0.19a. It was first released as a binary on August 4, 2002 at version 0.05a. The source was first released at version 0.02 and it was published on SourceForge on July 6, 2002. Over time 7 more developers joined the effort. Merkur) who was dissatisfied by the original eDonkey2000 client. The eMule project was started on May 13, 2002 by Hendrik Breitkreuz (a.k.a. . eMule is coded in Visual C++ .NET using the Microsoft Foundation Classes and because it is a popular open-source program, hundreds of eMule mods (modifications of the original eMule) have appeared on the Internet. Matching file sources is verified through the use of the MD4 algorithm. Recently, many of the sites which provide these links have been taken offline by authorities due to accusations of copyright infringement, as well as a questionable legality of the links they provide. These links ensure that the file being downloaded shares the same hash, and therefore is not a "fake". Another feature of eMule is the ability to accept "ed2k" links from a web browser and begin downloading the file(s) these links refer to. Furthermore eMule transmits data in (Zlib-)compressed form to save bandwidth. The distinguishing features of eMule are the direct exchange of sources between client nodes, fast recovery of corrupted downloads, and the use of a credit system to reward frequent uploaders. eMule runs on Microsoft Windows; however, its codebase forms the basis for a Linux client, xMule, and a multiplatform client, aMule. eMule is open source software released under the GNU General Public License. In computing, eMule is a peer to peer file sharing application that works with both eDonkey and Kad Network and has more features than the eDonkey client. Number of concurrent shared files: ~600 million. latest users statistics can be found at : Slyck.com). Number of concurrent users : 3 - 5 million (correct number is unknown since many new servers are faking their number of users. Your own credits cannot be displayed. This prevents faking the credits. Your own credits are saved by the client who owes you the credit. The unique user hash is used to identify the client. Credits are stored in the clients.met file. They are exchanged between two specific clients. Credits are not global. Not supporting clients will grant you no credits when you upload to them. It does not matter if the client supports the credit system or not. All Clients uploading to you are rewarded by the credit system. Otherwise, the credit value is x. If x is greater than 10, the credit value is 10. If x is less than 1, the credit value is 1. Call it x. Out of those two values, choose the one that is lower. Calculate the following value: Square root of total uploaded data + 2. Calculate the following value: total uploaded data × 2 / total downloaded data. Otherwise:
|