I implemented a ssh conection from the outside to my intranet. This ssh requires a username and a password.
In terms of security what is more secure: require authentication (username and password) or having the public key of each user that connects to our intranet in the
authorized public key lists (in this case there is no need for username and password)?
In the second case there is no need of authentication and only the users wich have the public keys in the list are allowed to enter in my intranet.
This second solution is a good solution or that brings other security problems ?
"Keep your friends close, but your enemies closer."
"Do or do not. There is no try" - Yoda
I feel erroneusly (?) secure after .host.denyed in.telnetd and
in.sshd from everywhere except one pc, which is denying all exept
keyboard. I belive that if i can keep hosts.deny and hosts.allow files
safe, and from time to time patch most actual security holes i`ll be
conditionaly safe. Em i wrong? Probably I do.
I just cant imaginate how system can be cracked in lower stage, so
that is my problem. I heard that inetd is very insecure, and some
peoples using tcpd (or soundlike).
I run harden_suse, but was forced to answer 8/10 to no, as my server
should provide a lot of public services, and have world writible
directories as well. And thats right - this script was developed not
for systems like mine one. However i`ll run SuSE-firewall-3.0 script,
to make my system even stronger. But thats all. I dont know what can i
do else. I should keep folowing services open:
httpd; smptd; pop3d; ftpd; snmpd; named; inetd; sshd; nscd.
So if you know how to keep them at minimal risk, or know some holes at
those, i would be very gratefull for any info and/or tips.
I dont ask to do work for me - link to good manual would be nice too.
By the way i have SuSE 6.3 (2.2.13).
Thanks in advice.
Gediminas Grigas mailto:email@example.com
umm, I have a small problem.
When setting up our server, I tried to get the best security as possible.
Maybe I changed some config-file to fit our needs to allow ssh-logins only
from specified users.(But I have no idea which file this was :-(( )
Now I want to allow another user to login using ssh.
I made ssh-keygen for this user, entered the password, copied identity.pub
to authorized_keys in the .ssh-directory.
But when trying to login via ssh, servers sends permission denied.
What else must be done ?
Does anyone know if PGP works with Netscape's Messenger? I was at
the pgp site and it listed a lot of mail clients, no Netscape.
On the side of the software box, in the "System requirements section",
it said "Requires Windows 95 or better." So I installed Linux.
-----BEGIN PGP SIGNED MESSAGE-----
SuSE Security Announcement
Package: lprold <= 3.0.1
Date: Wed Oct 27 18:04:36 CEST 1999
Affected: all Linux distributions using the package mentioned above
A security hole was discovered in the package mentioned above.
Please update as soon as possible or disable the service if you are using
this software on your SuSE Linux installation(s).
Other Linux distributions or operating systems might be affected as
well, please contact your vendor for information about this issue.
Please note, that that we provide this information on as "as-is" basis only.
There is no warranty whatsoever and no liability for any direct, indirect or
incidental damage arising from this information or the installation of
the update package.
1. Problem Description
The file access permissions aren't properly checked by the lpr and
By exploiting this race condition a user could print files s/he hasn't
Update the package from our FTP server.
Here are the md5 checksums of the upgrade packages, please verify these
before installing the new packages:
6466274da4d258a75432321c065abdb5 lprold-3.0.44-0.i386.rpm (6.1, x86)
30249f92420d7818cb1654e61840dbb7 lprold-3.0.44-0.i386.rpm (6.2, x86)
c4b2dc82ff09414733a41ffc78a97d47 lprold-3.0.44-0.alpha.rpm (6.1, AXP)
You will find the update on our ftp-Server:
Webpage for patches:
or try the following web pages for a list of mirrors:
SuSE has got two free security mailing list services to which any
interested party may subscribe:
suse-security(a)suse.com - moderated and for general/linux/SuSE
security discussions. All SuSE security
announcements are send to this list.
suse-security-announce(a)suse.com - SuSE's announce-only mailing list.
Only SuSE's security annoucements are sent
to this list.
To subscribe, just send an emtpy message to suse-security-subscribe(a)suse.com
or suse-security-announce-subscribe(a)suse.com like this:
echo | mail suse-security-subscribe(a)suse.com
echo | mail suse-security-announce-subscribe(a)suse.com
If you want to report *NEW* security bugs in the SuSE Linux Distribution
please send an email to security(a)suse.de or call our support line.
You may use pgp with the public key below to ensure confidentiality.
This information is provided freely to everyone interested and may
be redistributed provided that it is not altered in any way.
Type Bits/KeyID Date User ID
pub 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de>
- -------BEGIN PGP PUBLIC KEY BLOCK-----
- -------END PGP PUBLIC KEY BLOCK-----
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
Does anyone know how to do a chroot for users logging in via SSH ?
You know, like the chroot that can automatically be done when ftp'ing onto
I don't want the users to be able to escape from their homedirs to higher
levels in the directory-tree.
I know that this can be done somehow, but couldn't find any hint on the net
nor in any howto.
Thanks in advance.
Stephan M. Ott // OKDesign oHG
Internet-Providing / Netzwerkmanagement
smo(a)okdesign.de ..... http://www.okdesign.de
tel. 09565-61397 ..... fax. 09565-61399
handy. 0171-8351130 oder 0171-7858064
Do the 3 vulnerabilities mentioned in the CERT advisory affect SuSe 6.2?
If so, when will there be an update?
< Selcuk Ozturk <+> >
< MIS Deputy Director <+> >
< Phone : (301)883-2482 <+> FDCH >
< Fax : (301)883-9754 <+> 1100 Mercantile Lane, Ste 119 >
< E-mail : sozturk(a)fdch.com <+> Largo, MD 20774 >
You may well be right. We have been attacked by a horde of "Meowers". I'm
actually having fun with them, but I don't like being in a situation where
they have the advantage over me. Can you tell me more about this poetry?
Andreas Kunberger wrote:
> I think it´s not encrypted: It´s thw famous VOGON poetry!!!
> At 25 Oct 99, um 22:49 Steven T. Hatton wrote:
> > The following message was posted to a news group. I tried to rot 13 it
> > and didn't seem to get any coherent message. I assueme it is encrypted
> > english. Does anybody have an idea how to crack it?
> > Sllipd hlo tenslu huusl nlb
> > eyb eupkmun mbnnsbx cku
> > gkfmp buk iew fier etfj
> > tnmr ijee rfg ehkm ew ba
> > sfsli tlnbkk ms sy!
> Andreas Kunberger
> Dipl.-Ing. Andreas Kunberger
> Institut fuer Textil- und Verfahrenstechnik
> Universitaet Stuttgart
At 12:30 25.10.1999 +0200, you wrote:
>I'm afraid you cannot build asymetric subnets. This is because
>subnets are generated by applying a bitmask to the former host part, which
>is just a mathematic operation like
>subnets=(2^former-host-bits/2^netmask-bits)-2. This means all subnets are of the same size.
you can build asymmetric subnets using "variable length subnet mask" or
CIDR (classless inter domain routing). You might want to give
your DMZ 64 IP addresses (thats a /26) and use just 4 IP addresses
for the subnet between the router and the firewall (/30).
It's important that the machines in the DMZ know only about
their /26 subnet and use a default route to the firewall.
The router needs only know how to reach the firewall, so
you configure its ethernet interface to be in the 4 IP subnet
as the external interface of the firewall and apply a static
route for the rest of the addresses to this firewall address.
If your router doesn't allow overlapping routes, you have to
stack several non-overlapping static routes that cover the
entire address space.
Example: your address space: 220.127.116.11-192.168.0.127
Router-FW-Subnet: 192.168.0.0/30 (192.168.0.1=router,
static routes: 192.168.0.4/30 => 192.168.0.2
192.168.0.8/29 => 192.168.0.2
192.168.0.16/28 => 192.168.0.2
192.168.0.32/27 => 192.168.0.2
192.168.0.64/26 => 192.168.0.2
or overlapping: 192.168.0.0/25 => 192.168.0.2