search for: uservents

[Mod: chat removed -- alex] From: userv-maint@chiark.greenend.org.uk (Ian Jackson) Approved: alex@yuriev.com To: linux-security@redhat.com Subject: userv - how to make cron (et al) not setuid 0. Introduction Some time ago I posted on linux-security to say that I was working on a client/server pair which would allow you to invoke a privileged service in a more secure manner. I''ve now

Hello, I just made available a beta version of a port scan detector that I''ve been working on. The program, called Abacus Sentry, is a port scan/probe detector that offers what I think are a number of unique and useful features: - Runs on TCP or UDP sockets. Configurable by the user to bind to multiples of sockets for increased detection coverage. - Adjustable scan detection value with

Many of the security problems we''ve had to deal with recently have been where one program invokes another when no good level of trust exists between them. Currently solutions to this requirement are produced on an ad-hoc basis, usually involving set-id programs (often setuid root), superuser daemons calling user programs for `upcalls'', or both. There are problems with this

...it be a right move to rely on UserEvents instead ? Then I would specifically have to add those UserEvents in dialplan but I'm afraid to be unable to support things like hangups or transfers, ... What's your opinion about that ? Would you "filter system events" or "add custom uservents" ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090422/6fa497f5/attachment.htm

I am running the following migration with PostgreSQL 8.2.5. It works fine on my Windows machine, but gives me the below error on Linux CentOS 4.3. Any ideas? Thanks, Chirag class CreateUsers < ActiveRecord::Migration def self.up create_table :uers do |t| t.column :timestamp, :timestamp_with_time_zone t.column :userval, :integer, :limit => 1, :null=> false #will use

Hi Andrew, thanks for you information, but I have some question, I'm not a samba expert... Sorry! Not that issue, but a very well known one. The trouble is, Samba 4.4 was happy to get a tree like this: X | | Y Z in an order like this: Step 1 Y Step 2 Y Z Step 3 X | | Y Z As long as everything worked out in the end, it was fine. But this had issues, so we patched it to instead

Hi folks, I''m having an issue with rsync between my firewall and an internal box. It seems to be a shorewall issue (or correctly speaking, an issue with my shorewall config) because if I disable shorewall my rsync works fine. And I just can''t find it documented anywhere what I need to do. I have rules like this : root@userver:/etc/shorewall# grep -i Rsync rules

Just a quick note for the developers, so we can find this in the list archives when we need it... Xapian is now pointing at a mirror of the swig SVN repository, hosted on the same machine as xapian. This avoids having to contact a separate machine whenever doing a full svn update, and means checkouts should happen faster (since sourceforge is pretty slow...) and we're no longer at risk

Hi, About duplicate issues warning during join, What I can do to find and solve this errors? I like to investigate source of this issue and solve this errors before join Thanks Missatge de Trenta sis <trenta.sis at gmail.com> del dia dt., 10 de set. 2019 a les 11:14: > > Hi, > > About duplicate issues warning during join, What I can do to find and > solve this errors? >

On Mon, 2019-09-09 at 10:33 +0200, Trenta sis via samba wrote: > Hi, > > After reading wiki documentation about join I have tested to join a > second dc, but with problems. > > I need to add a second controller to our AD, and then upgrade existing > server (4.4.5) and I have tried to join a new DC 4.10.7 to 4.4.5 > server but I receive join errors, attached output wit

On Thu, 2019-09-19 at 09:49 +0200, Trenta sis via samba wrote: > hi > Sorry, error is > > ldb_key_value/ldb_kv_index.c:2413: duplicate attribute value in > CN=server,OU=servers,DC=DOMIAN,DC=COM for index on > servicePrincipalNAme, duplicate og objectGUID > 931a3f57-1062-423e-9488-695700b197b0 in > @INDEX:SERVICEPRINCIPALNAME:WSMAN/OLD-SERVER > > multiple errors liek

Hi, About duplicate issues warning during join, What I can do to find and solve this errors? Thanks Missatge de Trenta sis <trenta.sis at gmail.com> del dia dl., 9 de set. 2019 a les 15:53: > > Hi Andrew, > > thanks for you information, but I have some question, I'm not a samba > expert... Sorry! > > Not that issue, but a very well known one. > > The trouble

hi Sorry, error is ldb_key_value/ldb_kv_index.c:2413: duplicate attribute value in CN=server,OU=servers,DC=DOMIAN,DC=COM for index on servicePrincipalNAme, duplicate og objectGUID 931a3f57-1062-423e-9488-695700b197b0 in @INDEX:SERVICEPRINCIPALNAME:WSMAN/OLD-SERVER multiple errors liek this during join. Not sure where is the issue and how to solve? With this error join is correct and both samba

Hi, After reading wiki documentation about join I have tested to join a second dc, but with problems. I need to add a second controller to our AD, and then upgrade existing server (4.4.5) and I have tried to join a new DC 4.10.7 to 4.4.5 server but I receive join errors, attached output wit and without debug: I have executed samba-tool dbcheck --cross-ncs all seems OK I have made a test

Package: logcheck-database Version: 1.3.13 Severity: normal The rule for SSH ignoring "Bad protocol version identification" assumes there are no single quotes inside the version string ('[^']'). I am however getting mails including those lines: Mar 25 22:57:04 Debian-60-squeeze-64-minimal sshd[12144]: Bad protocol version identification

Package: logcheck-database Version: 1.3.8 Severity: wishlist HI, can you please create a rule/some rules for amavis(d-new). I get for every mail this mesage: May 25 19:55:40 data amavis[9603]: (09603-15) Passed CLEAN, [::1] [213.165.64.22] <xxx at yyy.zz> -> \ <aaa at localhost>, Message-ID: <20100525175015.29677page1 at mx002.bbb.ccc>, mail_id: MM7upJv6se1Z, \ Hits:

Package: logcheck-database Version: 1.3.13 Severity: normal Tags: patch After upgrading to debian squeeze I get several messages a day in the form of: Jul 2 15:05:15 hostname spamd[21286]: spamd: handled cleanup of child pid [28609] due to SIGCHLD: exit 0 This is due to an update in spamd, that makes the message more detailed (includes exit code)[1]. Therefore messages including exit code 0