Office
Online is an online office suite offered by Microsoft, which allows
users to create and edit files using lightweight Microsoft Office web
apps: Word, Excel, PowerPoint and OneNote. Wikipedia
Date launched: June 7, 2010
Office Online
Tuesday, June 19, 2018
Fing
Discover which devices are connected to any Wi-Fi network, map devices, detect intruders, assess network security risks, troubleshoot network problems and achieve best network performance, with the world’s most popular network toolkit.
With more than a dozen free network tools including; Wi-Fi scanner, port scanner, DNS lookup, ping and service monitoring – Fing is a must-have network utility.
Fing network utilities include:
+ Wi-Fi/LAN scanner: discover all devices connected to any network
+ Full device details including IP address, MAC address, Device Name, Vendor, Device Manufacturer and more
+ Advanced analysis of NetBIOS, UPNP and Bonjour names, properties and device types
+ Inventory of devices and networks
+ Internet connectivity checker
+ ISP analysis and location
+ Subnet scanner
+ Port scanner: TCP port scanning that automatically finds open ports and available services
+ Ping and traceroute: for network quality measurement
+ WOL: remotely wake up devices
+ DNS Lookup and reverse DNS lookup
+ Connect to ports (Browser, SSH, FTP)
+ Network intruder detection
+ Network monitoring: device online and offline tracking
+ Supports device identification by IP address for bridged networks
Together with its add-on Fingbox hardware, you may also:
+ Block devices and pause Internet connection
+ Analyze the usage of bandwidth
+ Find the Wi-Fi Sweet Spot
+ Verify your Internet Speed
+ Troubleshoot your Internet connection
+ Monitor the Digital Presence on your network
+ Protect your network with a wireless Digital Fence that continuously watches over Wi-Fi devices around you.
Download
Squid - Proxy Server
Squid - Proxy Server
Squid is a full-featured web proxy cache server application
which provides proxy and cache services for Hyper Text
Transport Protocol (HTTP), File Transfer Protocol (FTP), and
other popular network protocols. Squid can implement
caching and proxying of Secure Sockets Layer (SSL) requests
and caching of Domain Name Server (DNS) lookups, and perform
transparent caching. Squid also supports a wide variety of
caching protocols, such as Internet Cache Protocol (ICP),
the Hyper Text Caching Protocol (HTCP), the Cache Array
Routing Protocol (CARP), and the Web Cache Coordination
Protocol (WCCP).
The Squid proxy cache server is an excellent solution to a
variety of proxy and caching server needs, and scales from
the branch office to enterprise level networks while providing
extensive, granular access control mechanisms, and
monitoring of critical parameters via the Simple Network
Management Protocol (SNMP). When selecting a computer system
for use as a dedicated Squid caching proxy server for many
users ensure it is configured with a large amount of physical
memory as Squid maintains an in-memory cache for increased
performance.
Installation
At a terminal prompt, enter the following command to install the Squid server:
sudo apt install squid
Configuration
Squid is configured by editing the directives contained within the /etc/squid/squid.conf
configuration file.
The following examples illustrate some of the directives
which may be modified to affect the behavior of the Squid server.
For more in-depth configuration of Squid, see the References
section.
Prior to editing the configuration file, you should make a copy of the original file and protect it
from writing so you will have the original settings as a reference, and to re-use as necessary. Make this copy
and protect it from writing using the following commands:
sudo cp /etc/squid/squid.conf /etc/squid/squid.conf.original sudo chmod a-w /etc/squid/squid.conf.original
-
To set your Squid server to listen on TCP port 8888 instead of the default TCP port 3128, change the http_port directive as such:
http_port 8888
-
Change the visible_hostname directive in order to give the Squid server a specific hostname. This hostname does not necessarily need to be the computer's hostname. In this example it is set to weezie
visible_hostname weezie
-
Using Squid's access control, you may configure use of Internet services proxied by Squid to be available only users with certain Internet Protocol (IP) addresses. For example, we will illustrate access by users of the 192.168.42.0/24 subnetwork only:Add the following to the bottom of the ACL section of your /etc/squid/squid.conf file:
acl fortytwo_network src 192.168.42.0/24
Then, add the following to the top of the http_access section of your /etc/squid/squid.conf file:http_access allow fortytwo_network
-
Using the excellent access control features of Squid, you may configure use of Internet services proxied by Squid to be available only during normal business hours. For example, we'll illustrate access by employees of a business which is operating between 9:00AM and 5:00PM, Monday through Friday, and which uses the 10.1.42.0/24 subnetwork:Add the following to the bottom of the ACL section of your /etc/squid/squid.conf file:
acl biz_network src 10.1.42.0/24 acl biz_hours time M T W T F 9:00-17:00
Then, add the following to the top of the http_access section of your /etc/squid/squid.conf file:http_access allow biz_network biz_hours
After making changes to the /etc/squid/squid.conf file, save the file and restart the squid
server application to effect the changes using the following command entered at a terminal prompt:
sudo systemctl restart squid.service
If formerly a customized squid3 was used that set up the spool at /var/log/squid3 to be a mountpoint, but otherwise kept the default configuration the upgrade will fail.
The upgrade tries to rename/move files as needed, but it can't do so for an active mountpoint.
In that case please either adapt the mountpoint or the config in /etc/squid/squid.conf so that they match.
The same applies if the include config statement was used to pull in more files from the old path at /etc/squid3/.
In those cases you should move and adapt your configuration accordingly.
References
Apache Server
What is the Apache HTTP Server Project?
The Apache HTTP Server Project is a collaborative software development effort aimed at creating a robust, commercial-grade, featureful, and freely-available source code implementation of an HTTP (Web) server. The project is jointly managed by a group of volunteers located around the world, using the Internet and the Web to communicate, plan, and develop the server and its related documentation. This project is part of the Apache Software Foundation. In addition, hundreds of users have contributed ideas, code, and documentation to the project. This file is intended to briefly describe the history of the Apache HTTP Server and recognize the many contributors.How Apache Came to Be
In February of 1995, the most popular server software on the Web was the public domain HTTP daemon developed by Rob McCool at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign. However, development of that httpd had stalled after Rob left NCSA in mid-1994, and many webmasters had developed their own extensions and bug fixes that were in need of a common distribution. A small group of these webmasters, contacted via private e-mail, gathered together for the purpose of coordinating their changes (in the form of "patches"). Brian Behlendorf and Cliff Skolnick put together a mailing list, shared information space, and logins for the core developers on a machine in the California Bay Area, with bandwidth donated by HotWired. By the end of February, eight core contributors formed the foundation of the original Apache Group:- Brian Behlendorf
- Roy T. Fielding
- Rob Hartill
- David Robinson
- Cliff Skolnick
- Randy Terbush
- Robert S. Thau
- Andrew Wilson
- Eric Hagberg
- Frank Peters
- Nicolas Pioch
The early Apache server was a big hit, but we all knew that the codebase needed a general overhaul and redesign. During May-June 1995, while Rob Hartill and the rest of the group focused on implementing new features for 0.7.x (like pre-forked child processes) and supporting the rapidly growing Apache user community, Robert Thau designed a new server architecture (code-named Shambhala) which included a modular structure and API for better extensibility, pool-based memory allocation, and an adaptive pre-forking process model. The group switched to this new server base in July and added the features from 0.7.x, resulting in Apache 0.8.8 (and its brethren) in August.
After extensive beta testing, many ports to obscure platforms, a new set of documentation (by David Robinson), and the addition of many features in the form of our standard modules, Apache 1.0 was released on December 1, 1995.
Less than a year after the group was formed, the Apache server passed NCSA's httpd as the #1 server on the Internet and according to the survey by Netcraft , it retains that position today.
In 1999, members of the Apache Group formed the Apache Software Foundation to provide organizational, legal, and financial support for the Apache HTTP Server. The foundation has placed the software on a solid footing for future development, and greatly expanded the number of Open Source software projects, which fall under this Foundation's umbrella.
Getting Involved
If you just want to send in an occasional suggestion/fix, then you can simply use the bug reporting form at < http://httpd.apache.org/bug_report.html >. You can also subscribe to the announcements mailing list (announce@httpd.apache.org)
which we use to broadcast information about new releases, bugfixes, and
upcoming events. There's a lot of information about the development process
(much of it in serious need of updating) to be found at <
http://httpd.apache.org/dev/ >.NOTE: The developer mailing list is NOT a user support forum; it is for people actively working on development of the server code. There is also a 'docs' subproject for those who are actively developing and translating the documentation. If you have user/configuration questions, subscribe to the Users list or try the USENET newsgroups " " or " " (as appropriate for the platform you use).
Development
There is a core group of contributors, formed initially of the project founders, and augmented from time to time by other outstanding contributors. There are 'committers', who are granted access to the source code control repositories to help maintain the project or docs, and the core group now managing the project, which is called the Apache HTTP Project Management Committee (PMC, for short). In fact, each Apache Software Foundation project has its own PMC, to determine committers, project direction and overall management. The terms "The Apache Group" or "Apache Core" are no longer used.The project is a meritocracy -- the more work you have done, the more you will be allowed to do. The group founders set the original rules, but they can be changed by vote of the active PMC members. There is a group of people who have logins on our server and access to the source code repositories. Everyone has read-only access to the repositories. Changes to the code are proposed on the mailing list and usually voted on by active members -- three +1 ('yes' votes) and no -1 ('no' votes, or vetoes) are needed to commit a code change during a release cycle; docs are usually committed first and then changed as needed, with conflicts resolved by majority vote.
Our primary method of communication is our mailing list. Approximately 40 messages a day flow over the list, and are typically very conversational in tone. We discuss new features to add, bug fixes, user problems, developments in the web server community, release dates, etc. The actual code development takes place on the developers' local machines, with proposed changes communicated using a patch (output of a unified "diff -u oldfile newfile" command), and then applied to the source code control repositories by one of the committers. Anyone on the mailing list can vote on a particular issue, but only those made by active members or people who are known to be experts on that part of the server are counted towards the requirements for committing. Vetoes must be accompanied by a convincing technical justification.
New members of the Apache HTTP Project Management Committee are added when a frequent contributor is nominated by one member and unanimously approved by the voting members. In most cases, this "new" member has been actively contributing to the group's work for over six months, so it's usually an easy decision.
The project guidelines continuously evolve under the oversight of the PMC, as the membership of the group changes and our development/coordination tools improve.
Why Apache Software is Free
Apache Software exists to provide robust and commercial-grade reference implementations of many types of software. It must remain a platform upon which individuals and institutions can build reliable systems, both for experimental purposes and for mission-critical purposes. We believe that the tools of online publishing should be in the hands of everyone, and that software companies should make their money by providing value-added services such as specialized modules and support, amongst other things. We realize that it is often seen as an economic advantage for one company to "own" a market - in the software industry, that means to control tightly a particular conduit such that all others must pay for its use. This is typically done by "owning" the protocols through which companies conduct business, at the expense of all those other companies. To the extent that the protocols of the World Wide Web remain "unowned" by a single company, the Web will remain a level playing field for companies large and small. Thus, "ownership" of the protocols must be prevented. To this end, the existence of robust reference implementations of various protocols and application programming interfaces, available free to all companies and individuals, is a tremendously good thing.Furthermore, the Apache Software Foundation is an organic entity; those who benefit from this software by using it, often contribute back to it by providing feature enhancements, bug fixes, and support for others in public lists and newsgroups. The effort expended by any particular individual is usually fairly light, but the resulting product is made very strong. These kinds of communities can only happen with freely available software -- when someone has paid for software, they usually aren't willing to fix its bugs for free. One can argue, then, that Apache's strength comes from the fact that it's free, and if it were made "not free" it would suffer tremendously, even if that money were spent on a real development team.
We want to see Apache Software used very widely -- by large companies, small companies, research institutions, schools, individuals, in the intranet environment, everywhere -- even though this may mean that companies who could afford commercial software, and would pay for it without blinking, might get a "free ride" by using Apache. We are even happy when some commercial software companies completely drop their own HTTP server development plans and use Apache as a base, with the proper attributions as described in the LICENSE. That is to say, the Apache HTTP Sever only comes from the Apache Software Foundation, but many vendors ship their own product "based on the Apache {Project}". There is no "{Vendor} Apache {Product}", this is an abuse of the Apache Software Foundation's marks.
Downloading the Apache HTTP Server
Use the links below to download the Apache HTTP Server from one of our mirrors. You must verify the integrity of the downloaded files using signatures downloaded from our main distribution directory.Only current recommended releases are available on the main distribution site and its mirrors. Historical releases, including the 1.3, 2.0 and 2.2 families of releases, are available from the archive download site.
Apache httpd for Microsoft Windows is available from a number of third party vendors.
Stable Release - Latest Version:
- 2.4.33 (released 2018-03-17)
Mirror
The currently selected mirror is http://www-us.apache.org/dist/. If you encounter a problem with this mirror, please select another mirror. If all mirrors are failing, there are backup mirrors (at the end of the mirrors list) that should be available.You may also consult the complete list of mirrors.
Apache HTTP Server 2.4.33 (httpd): 2.4.33 is the latest available version 2018-03-17
The Apache HTTP Server Project is pleased to announce the release of version 2.4.33 of the Apache HTTP Server ("Apache" and "httpd"). This version of Apache is our latest GA release of the new generation 2.4.x branch of Apache HTTPD and represents fifteen years of innovation by the project, and is recommended over all previous releases!For details, see the Official Announcement and the CHANGES_2.4 and CHANGES_2.4.33 lists.
-
Source: httpd-2.4.33.tar.bz2
[ PGP ] [
MD5 ] [
SHA1 ] [
SHA256 ]
-
Source: httpd-2.4.33.tar.gz [
PGP ] [
MD5 ] [
SHA1 ] [
SHA256 ]
-
Binaries
-
Security and official patches
-
Other files
-
Files for Microsoft Windows
Apache mod_fcgid FastCGI module for Apache HTTP Server released as 2.3.9 2013-10-08
The Apache Software Foundation and the Apache HTTP Server Project are pleased to announce the release of version 2.3.9 of mod_fcgid, a FastCGI implementation for Apache HTTP Server versions 2.2 and 2.4. This version of mod_fcgid is a security release.For information about this module subproject, see the mod_fcgid module project page.
-
Source as gzip with LF line endings:
mod_fcgid-2.3.9.tar.gz
[
PGP
] [
MD5
] [
SHA1
]
-
Source as bz2 with LF line endings:
mod_fcgid-2.3.9.tar.bz2
[
PGP
] [
MD5
] [
SHA1
]
-
Win32, Netware or OS/2 Source with CR/LF line endings:
mod_fcgid-2.3.9-crlf.zip
[
PGP
] [
MD5
] [
SHA1
]
Apache FTP module for Apache HTTP Server released as 0.9.6-beta 2008-10-08
The Apache HTTP Server Project is pleased to announce the release of Apache FTP module for Apache HTTP Server, version 0.9.6 as beta.Users are encouraged to test and provide feedback on this beta release. For information about this module subproject, see the mod_ftp module project page.
-
Source with LF line endings (bzip2 compressed):
mod_ftp-0.9.6-beta.tar.bz2
[
PGP
] [
SHA1
] [
MD5
]
-
Source with LF line endings (gzip compressed):
mod_ftp-0.9.6-beta.tar.gz
[
PGP
] [
SHA1
] [
MD5
]
-
Win32, Netware or OS/2 Source with CR/LF line endings:
mod_ftp-0.9.6-beta-crlf.zip
[
PGP
] [
SHA1
] [
MD5
]
Verify the integrity of the files
It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases.The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the
asc
signature file for the relevant distribution. Make sure you get these files
from the main distribution directory ,
rather than from a mirror. Then verify the signatures using% pgpk -a KEYS
% pgpv httpd-2.4.33.tar.gz.asc
or
% pgp -ka KEYS
% pgp httpd-2.4.33.tar.gz.asc
or
% gpg --import KEYS
% gpg --verify httpd-2.4.33.tar.gz.asc httpd-2.4.33.tar.gz-
httpd-2.4.33.tar.* are signed by Daniel Ruggeri
1AD84DFF
-
httpd_2.4.16-netware-*.zip signed by Guenter Knauf
E55B0D0E(31D9665F)
-
mod_fcgid-2.3.9.tar.* and mod_fcgid-2.3.9-crlf.zip are signed by Jeff
Trawick
39FF092C
-
mod_ftp-0.9.6-beta* are signed by William A Rowe Jr
B55D9977(7F7214A7)
md5 or md5sum is included in many unix distributions. It
is also available as part of GNU
Textutils. Windows
users can get binary md5 programs from here
, here , or
here. An MD5 signature consists of 32 hex
characters, and a SHA1 signature consists of 40 hex characters. Ensure your
generated signature string matches the signature string published in the
files above.WampServer
WampServer,
a Windows web development environment.
WampServer is a Windows web development environment. It allows
you to create web applications with Apache2, PHP and a MySQL database.
Alongside, PhpMyAdmin allows you to manage easily your databases.
Start using WampServer
Start with WampServer
WampServer installs automatically all you need to start
developing web applications and is very intuitive to use. You will be
able to tune your server without even touching the setting files.
Installing
- Double click on the downloaded file and just follow the instructions. Everything is automatic. The WampServer package is delivered whith the latest releases of Apache, MySQL and PHP.
- Once WampServer is installed, you can manually add aditionals Apache, Php or MySql (only VC9, VC10 and VC11 compiled) versions. Explanations will be provided on the forum.
- Each release of Apache, MySQL and PHP has its own settings and its own files (datas for MySQL).
- The “www” directory will be automatically created (usually c:\wamp\www)
- Create a subdirectory in “www” and put your PHP files inside.
- Click on the “localhost” link in the WampSever menu or open your internet browser and go to the URL : http://localhost
Functionalities
WampServer’s functionalities are very complete and easy to use so we won’t explain here how to use them.With a left click on WampServer’s icon, you will be able to:
- manage your Apache and MySQL services
- switch online/offline (give access to everyone or only localhost)
- install and switch Apache, MySQL and PHP releases
- manage your servers settings
- access your logs
- access your settings files
- create alias
- change WampServer’s menu language
- access this page
Downloads
WampServer is available for free
(under GPML license) in two distinct versions : 32 and 64
bits. Wampserver 2.5 is not compatible with Windows XP, neither with
SP3, nor Windows Server 2003. Older WampServer versions are available on
SourceForge.
Wampserver
WampServer 64 bits (x64) 3.0.6
– Wampserver 3.1.0 64 bit x64 –
Apache 2.4.27 – PHP 5.6.31, 7.0.23, 7.1.9 – MySQL 5.7.19 – MariaDB
10.2.8 – PhpMyAdmin 4.7.4 – Adminer 4.3.1 – PhpSysInfo 3.2.7
changelog
WampServer 32 bits (x86) 3.0.6
Wampserver 3.1.0 32 bit x86 –
Apache 2.4.27 – PHP 5.6.31, 7.0.23, 7.1.9 – MySQL 5.7.19 – MariaDB
10.2.8 – PhpMyAdmin 4.7.4 – Adminer 4.3.1 – PhpSysInfo 3.2.7changelog
Transmission
Transmission is a cross-platform BitTorrent client that is:
Open Source.
Transmission is an open source, volunteer-based project. Unlike some BitTorrent clients, Transmission doesn't play games with its users to make money:- Transmission doesn't bundle toolbars, pop-up ads, flash ads, twitter tools, or anything else.
- It doesn't hold some features back for a payware version.
- Its source code is available for anyone to review.
- We don't track our users, and our website and forums have no third-party ads or analytics.
Easy.
Transmission is designed for easy, powerful use. We've set the defaults toJust Workand it only takes a few clicks to configure advanced features like watch directories, bad peer blocklists, and the web interface. When Ubuntu chose Transmission as its default BitTorrent client, one of the most-cited reasons was its easy learning curve.
Lean.
In separate benchmarks, Linux Format and Lacrocivious both found Transmission to use less CPU than any other GUI client. It even used less CPU than some non-GUI clients.Transmission also has the lowest memory footprint of any major BitTorrent client.
Imageshack chose Transmission for its BitTorrent farms because the competition
requires amounts of memory several times greater than Transmission.
Transmission's small footprint is one reason why many home device manufacturers, such as FON, Belkin, and Networked Media Tank ship with Transmission. When Belkin and Vuze Inc. partnered to write a
Torrent Genieto let people who ran Vuze and owned a Belkin router keep sharing files even when Vuze wasn't running, they decided to use Transmission -- not Vuze's own BitTorrent client -- on the router.
Native.
Download Transmission
The current release version is 2.94
Mac OS X
Source Code
Windows (early preview)
transmission-2.94-x86.msi
transmission-2.94-x64.msi
Requires Windows 7 or later
Nightly builds
SHA256 Hashes
Transmission-2.94.dmg: 2cae915ae0e37fc5983406ca7fbd53a054a7153d3bfd7a6cef117a8a28d8a78atransmission-2.94.tar.xz: 35442cc849f91f8df982c3d0d479d650c6ca19310a994eccdaa79a4af3916b7d
transmission-2.94-x86.msi: 9083bed824d707e8791f53811aaa88def8047d40f221a8e823571c103cf3aff6
transmission-2.94-x64.msi: a35672252661f16382072fd0ae87b8eafd47f5535439336fe2f161a542f9a1ab
Unix Distros
Ubuntu
Fedora
OpenSUSE
Mandriva
Subscribe to:
Posts (Atom)
