Once again, the OpenBSD project is asking for donations to keep its operations in motion. It doesn't ask for much -- U.S. $100,000 (small potatoes in the operating system development industry) -- yet it provides so much to the software world. Even if you don't use OpenBSD, you're likely to be benefiting from it unknowingly. If you're using Solaris, SCO UnixWare, OS X, SUSE Linux, or Red Hat Enterprise Linux, chances are you're using the OpenBSD-developed OpenSSH for secure shell access to remote machines. If so many are using this software, why are so few paying for it? Official responses (and non-responses) from Sun Microsystems, IBM, Novell, and Red Hat are below, but if you're one of the freeloaders who hasn't contributed to OpenBSD or OpenSSH, what's your excuse? . "Bigger than OpenBSD, our big contribution is OpenSSH," OpenBSD project leader Theo de Raadt told me in a 2004 interview. "It is now included in pretty much every non-Windows operating system made. It is included in network switches, in half of Cisco's products, and who knows where else. It is used by everything from Arrecibo to the Greek Army to who knows where else. And what have we gotten for it in return? Pretty much nothing at all." The link for this article located at Jem Report is no longer available. . The OpenBSD team convenes to strategize on maintaining OpenSSH, vital for safe shell access on various systems.. OpenBSD Contributions, Software Development, Open Source Projects. . LinuxSecurity.com Team
Telnet, Rsh, Rlogin, Rcp, and FTP are commonly used methods to access files and execute commands on remote servers. They are available in most operating systems and work seamlessly in multi-platform environments. However, this convenience comes with major security risks. This document is intended for IT professionals at enterprises who need to secure file transfer and system administration access methods in heterogeneous and large-scale environments. . The document describes common vulnerabilities and known exploits of plaintext file transfer and terminal connections. Also, eight areas to examine when seeking and evaluating products and technologies for an FTP and Telnet replacement are introduced. Finally, a cost-effective security approach based on Secure Shell for cross-platform, large-scale environments is introduced. The link for this article located at Net-Security.org is no longer available. . Securing plaintext file transfers and terminal connections is vital, as they expose sensitive data to interception. Switching to SFTP and SSH enhances security significantly. Secure Shell Solutions, File Transfer Security, Remote Access Protocols. . Benjamin D. Thomas
SSH is a secure replacement for telnet, rlogin, other r* and ftp protocols which handle sensitive information in an unsecure manner. Telnet broadcasts sensitive information such as usernames and passwords unencrpyted whereas SSH encrypts them, so that a malicious user trying . . . . SSH is a secure replacement for telnet, rlogin, other r* and ftp protocols which handle sensitive information in an unsecure manner. Telnet broadcasts sensitive information such as usernames and passwords unencrpyted whereas SSH encrypts them, so that a malicious user trying to retrieve them with a, i.e. some sniffer could have no use for them as such. Not only telnet is vulnerable to eavesdropping, many other network services behave in such unsecure manner. SSH stands for Secure Shell, and is the best solution so far for these. All those services (telnet, rlogin and such) are a menace for security of your systems, so if you're still using them, well... stop! Use SSH. Not sure nor convinced? Read on. The link for this article located at Help Net Security is no longer available. . Protect your network integrity using SSH, an encrypted substitute for less secure methods such as telnet and ftp when handling confidential information.. SSH, Secure Shell, Remote Access, Encryption, Network Security. . LinuxSecurity.com Team
Most corporations allow users to access the outside world for HTTP, FTP & Telnet. However, access via "Secure Shell" is often blocked (as was my situation in Corporate America). There is a work-around that is pretty easy.. . .. Most corporations allow users to access the outside world for HTTP, FTP & Telnet. However, access via "Secure Shell" is often blocked (as was my situation in Corporate America). There is a work-around that is pretty easy. Listed below are the four easy steps taken to get Secure Shell access without firewall changes: OS used = Linux, SuSE7.1 Pro, Linux Kernel 2.4 The link for this article located at LinuxNews is no longer available. The link for this article located at LinuxNews is no longer available. . Corporate networks frequently restrict Secure Shell connections. Discover simple methods to bypass these barriers by routing SSH through telnet ports.. SSH Client, Corporate Firewall, Secure Shell Workaround, Telnet Access. . LinuxSecurity.com Team
If you're a Linux administrator and you're still using telnet for authentication, your network could be in danger. Telnet passes your user IDs, password/passphrase, and the content of your terminal sessions in the clear, where anyone with a sniffer can see . . . . If you're a Linux administrator and you're still using telnet for authentication, your network could be in danger. Telnet passes your user IDs, password/passphrase, and the content of your terminal sessions in the clear, where anyone with a sniffer can see what you're doing regardless of whether they have your password. Secure Shell (SSH) is a protocol for secure terminal sessions over the Internet. This means you can control who gets into your servers with strong cryptography, keep passphrases from being transmitted in the clear over the Internet, and strongly encrypt as well as compress terminal sesions as they happen. The link for this article located at PlanetIT is no longer available. . As a systems administrator, relying on FTP can expose your data to risks. Transition to encrypted protocols today.. Secure Shell, SSH, Network Security, Encryption Best Practices. . LinuxSecurity.com Team
One of the coolest things about UNIX has been that there is not one but several different ways to administer systems from remote consoles. Sad to say, most of these methods (Telnet, rsh and X, to name a few) send everything . . . . One of the coolest things about UNIX has been that there is not one but several different ways to administer systems from remote consoles. Sad to say, most of these methods (Telnet, rsh and X, to name a few) send everything over the network in clear text, including passwords. The combination of our reliance on the Internet with the proliferation of script kiddies and other packet-sniffing deviants has made administrative clear-text network applications obsolete. But a few years ago Finnish über-hacker Tatu Ylonen created a mind-blowingly cool thing called the Secure Shell, or ssh. ssh is a suite of tools that roughly correspond to Sun's rsh, rcp and rlogin commands, but with one very important difference: paranoia. ssh lets you do everything rsh, rcp and rlogin do, using your choice of libertarian-grade encryption and authentication methods. But wait--there's a catch--ssh version 1 relies heavily on RSA, an excellent, but as we say, encumbered (patented) technology that requires any application that uses it to be licensed (paid for) unless it's used in noncommercial settings (even in noncommercial use ssh's legality has always been murky, especially in the US). But wait, you say, RSA's US patents expired in September 2000--problem solved, right? Almost: Tatu's got to earn a living, so by the time RSA became less encumbered, ssh itself had become more so as his company F-Secure tightened the licensing reins. In fact, beginning with ssh version 2.0, unlicensed/free commercial use (regardless of RSA issues) was no longer permitted. All this despite Tatu's sincere desire that ssh become an Internet standard, one of the requirements of which is that at least one free implementation be available. The link for this article located at Linux Journal is no longer available. . Delveinto the multifaceted applications of OpenSSH within UNIX systems, bolstering remote management and safeguarding network integrity through robust encryption techniques.. OpenSSH Uses, Remote Administration, Network Security Tools, Encryption Methods, UNIX Tools. . Anthony Pell
An OpenSSH-based Secure Shell is now available in the main NetBSD sources. And it will be pulled into the netbsd-1-5 branch, so it will be available in NetBSD 1.5. (ssh-1.2.27 and OpenSSH were already available in the NetBSD packages collection.). . .. An OpenSSH-based Secure Shell is now available in the main NetBSD sources. And it will be pulled into the netbsd-1-5 branch, so it will be available in NetBSD 1.5. (ssh-1.2.27 and OpenSSH were already available in the NetBSD packages collection.) According to an NetBSD announcement, the OpenSSH-based implementation is temporary. They believe it will be replaced within the next couple months with a "completely independent implementation". Other NetBSD mailing lists indicate that it is an independant, written-from-scratch, modular (protocols, crypto libraries, OS support, authentication mechanisms) and portable ssh implementation. It is not yet available to public, according to various mailing list postings, until a couple missing features are added. (OpenSSH is derived from the original ssh-1.2.12.) The new in-tree SSH uses new configuration filenames: /etc/sshd.conf and /etc/ssh.conf (instead of /etc/sshd_config for example). [all of article] The link for this article located at BSD Today is no longer available. . An implementation of Secure Shell using OpenSSH is now integrated into the core FreeBSD source for improved security and remote access.. Secure Shell, OpenSSH, NetBSD, SSH Implementation, Network Security. . Anthony Pell
In this article, I start by discussing the weaknesses of each of the these absolutely horrid protocols. I then introduce secure shell (ssh) and provide an in-depth guide to using it. Before some of you write this off, realize that if . . . . In this article, I start by discussing the weaknesses of each of the these absolutely horrid protocols. I then introduce secure shell (ssh) and provide an in-depth guide to using it. Before some of you write this off, realize that if you're still using passwords, you're not using ssh's strongest method of authentication. User-level public/private key authentication, somewhat similar to PGP signatures, is powerful and safe. Combine this with ssh-agent, which implements "single-signon," and you can save yourself hours a week, while remaining secure. The link for this article located at SecurityPortal is no longer available. . Outdated networking protocols pose significant risks to data integrity and confidentiality, making it essential to adopt modern alternatives like SSH for secure remote access.. Secure Shell, Protocol Weaknesses, Remote Access Security, SSH Authentication, Data Transfer. . Anthony Pell
Get the latest Linux and open source security news straight to your inbox.