Displaying 20 results from an estimated 54702 matches for "secures".
Did you mean:
secure
2008 Aug 26
0
Processed: The possibility of attack with the help of symlinks in some Debian
Processing commands for control at bugs.debian.org:
> tags 496359 security
Bug#496359: The possibility of attack with the help of symlinks in some Debian packages
There were no tags set.
Tags added: security
> tags 496360 security
Bug#496360: The possibility of attack with the help of symlinks in some Debian packages
Tags were: confirmed
Tags added: security
> tags 496362 security
2012 Nov 23
1
Public Key Authentication
Hi,
I wonder, how can i use openssh Public key authentification with
ActivCard pkcs11 x509 certificate store and login to only my account
reading/using username provided from certificate DN, or principal
name,friendly name ?
b111887 and e411617 is administrator on this os. I have rights to put
e411617 pub keys to b111887 home folder authorized keys. And because
openssh ask's me to provide
2010 Jun 17
0
Debian packages fixing CVE-2010-2063 are available for lenny
Quoting Karolin Seeger (kseeger at samba.org):
> Release Announcements
> =====================
>
> This is a security release in order to address CVE-2010-2063.
>
>
> o CVE-2010-2063:
> In Samba 3.3.x and below, a buffer overrun is possible in chain_reply code.
As this issue also affect the 3.2 series of samba (which is no longer
officially supported by the Samba
2015 Apr 08
4
Update only of security vulnerabilities?
Hi All :)
What is the best way to get a list of available security updates?
I found several commands for that:
1) yum updateinfo list updates -q --security
2) yum list-security --security -q
3) yum --security check-update -q
Based on the sample output below I think I can use any of the three with
some awk to get a list of packages.
yum updateinfo list updates -q --security
FEDORA-EPEL-2014-0525
2019 Nov 25
3
[RFC] LLVM Security Group and Process
On Tue, Nov 19, 2019 at 10:46 AM JF Bastien <jfbastien at apple.com> wrote:
> And I do agree that if someone were to come in and put in the significant
> amounts of work to make LLVM directly usable in security-sensitive places,
> then we could support that. But none of that should have anything to do
> with the security group or its membership. All of that work and discussion,
2019 Oct 01
1
[libnbd PATCH] docs: Add libnbd-security(1) man page
Copies heavily after a similar addition recently made in nbdkit.
---
I'm not sure if .1 or .3 fits better for the man page. With nbdkit,
.1 made sense because 'nbdkit' is a standalone program; but with
libnbd, our only standalone is nbdsh, yet naming it nbdsh-security
seems off.
docs/Makefile.am | 7 +++++++
docs/libnbd-security.pod | 32 ++++++++++++++++++++++++++++++++
2007 Apr 15
0
CentOS-announce Digest, Vol 26, Issue 5
Send CentOS-announce mailing list submissions to
centos-announce at centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-request at centos.org
You can reach the person managing the list at
centos-announce-owner at centos.org
When
2011 Mar 17
2
security updates?
Hello,
There are several important security updates available:
Critical: firefox security and bug fix update
Important: tomcat5 security update
Important: vsftpd security update
Moderate: subversion security and bug fix update
Important: logwatch security update
Important: libtiff security update
Moderate: kernel security and bug fix update
Important: samba security update
Important: samba3x
2007 Sep 19
1
LDAP / PAM -- Invalid Credentials Error
Hello,
I am having a small issue with LDAP, and I hope someone here might be
able to provide a few tips.
I am unable to authenticate as user 'testuser' on server 'storage'
and the following errors appear in /var/log/messages on server 'storage'
Sep 19 16:56:17 storage sshd(pam_unix)[3124]: check pass; user unknown
Sep 19 16:56:17 storage sshd(pam_unix)[3124]:
2004 Apr 06
4
SYN attacks
Heya,
FREEBSD 4.9-STABLE
Is there anyway to block SYN attacks and prevent it from bring down
my server?
Its been attacking for sometime.
2019 Nov 19
2
[RFC] LLVM Security Group and Process
On Mon, Nov 18, 2019 at 6:00 PM JF Bastien via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
>
> On Nov 18, 2019, at 2:42 PM, David Blaikie via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>
>
> On Mon, Nov 18, 2019 at 2:31 PM Robinson, Paul via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> One problem with defining away
2002 Nov 15
1
Winbind and Samba
Hi all, I was wondering if someone could lend a little assistance.
I recently setup SAMBA/Winbind to allow users to login to a Redhat 8 box
using their Windows NT Domain credentials. All is working well in that
regard.
The issue I am having is getting regular UNIX based users to be able to
login. The following is my PAM configuration. For example, if I try to
login as root, it does not work.
2019 Nov 15
17
[RFC] LLVM Security Group and Process
Hello compiler enthusiasts,
The Apple LLVM team would like to propose that a new a security process and an associated private LLVM Security Group be created under the umbrella of the LLVM project.
A draft proposal for how we could organize such a group and what its process could be is available on Phabricator <https://reviews.llvm.org/D70326>. The proposal starts with a list of goals for
2002 Nov 18
1
Help with PAM Config
I've installed SAMBA, Winbind etc and everything is working great for users
to login with GDM using DOMAIN+username
Although this is working, now I can no longer login as a generic Linux user
(ex. root). The following is my GDM file from /etc/pam.d/gdm
I wonder if someone might have a suggestion as to what it's missing to allow
Linux users to login?
#%PAM-1.0
auth required
2002 Jul 09
5
Cant Log Into Terminal Using Winbind
List,
I am unable to log into a terminal using Winbind service. I have the login file correctly modifyed and nsswitch too. I have the 2.2.5 version of SAMBA with the new winbind. SAMBA shares work great, so I think it is something else. I get this error in the messages log:
Jul 9 11:46:01 alblinux sshd(pam_unix)[5463]: check pass; user unknown
Jul 9 11:46:01 alblinux sshd(pam_unix)[5463]:
2019 Oct 01
0
[libnbd PATCH] docs: Add libnbd-security(1) man page
Copies heavily after a similar addition recently made in nbdkit.
---
docs/Makefile.am | 7 +++++++
docs/libnbd-security.pod | 32 ++++++++++++++++++++++++++++++++
docs/libnbd.pod | 1 +
Makefile.am | 1 +
.gitignore | 3 ++-
SECURITY | 14 ++++++++++++++
6 files changed, 57 insertions(+), 1 deletion(-)
create mode 100644
2003 Nov 18
0
Samba PDC trying rid null logins
> We are trying to have linux authenticate to linux server running samba
> 3.0. We have the XP Pro, 6.2 redhat, and 7.3 redhat machines. They all
> authenticate to the linux server but we are having problems with blank
> passwords or the user can type any password. We are using pam modules for
> the authentication on the client machines.
> I have included the config files for
2004 Apr 07
5
Changing `security@freebsd.org' alias
Hello Folks,
The official email address for this list is
`freebsd-security@freebsd.org'. Due to convention, there is an email
alias for this list: security@freebsd.org, just as there is for
hackers@ & freebsd-hackers@, arch@ & freebsd-arch@, and so on.
The security@freebsd.org alias has been the source of occassional
problems. Several times in the past, postings have been made to
2003 Nov 19
0
FW: Samba PDC trying rid null logins
> -----Original Message-----
> From: Reed, Tameika
> Sent: Monday, November 17, 2003 5:56 PM
> To: 'samba@lists.samba.org'
> Subject: Samba PDC trying rid null logins
>
>
>
>
> We are trying to have linux authenticate to linux server running samba
> 3.0. We have the XP Pro, 6.2 redhat, and 7.3 redhat machines. They all
> authenticate to the
2019 Nov 18
2
[RFC] LLVM Security Group and Process
I think it's great to make a policy for reporting security bugs.
But first, yes, we need to be clear as to what sorts of things we consider
as "security bugs", and what we do not. We need to be clear on this, both
for users to know what they should depend on, and for LLVM contributors to
know when they should be raising a flag, if they discover or fix something
themselves.
We could