search for: lock_un

There are conflicting reports about wether or not Red Hat 4.0 is vulnerable to the login-lockout described earlier. I have the impression that if you install the updates it will have been fixed. Approval of messages about this subject is now restricted to "here is a patch", and a vendors "We have made a patch available". Roger.

...,O_RDWR|O_CREAT|O_APPEND,S_IRUSR|S_IWUSR); if (flock(f, LOCK_EX)) { printf("Error locking"); exit; } printf("Text: "); scanf("%s",c); strcat(c,"\n"); write(f,c,strlen(c)); printf("Say something to quit: "); scanf("%s",c); if (flock(f, LOCK_UN)) { printf("Error unlocking"); exit; } close(f); Albert Cervera Areny

...8,10 @@ endutent(); if((wtmp = open(_PATH_WTMP, O_APPEND|O_WRONLY)) >= 0) { - flock(wtmp, LOCK_EX); +/* Locking wtmp allows for trivial denial of service attack by nvi */ +/* flock(wtmp, LOCK_EX); */ write(wtmp, (char *)&ut, sizeof(ut)); - flock(wtmp, LOCK_UN); +/* flock(wtmp, LOCK_UN); */ close(wtmp); } } [mod: WARNING: UNTESTED CODE, MANUALLY FABRICATED PATCH AHEAD. Anybody dare to test the following?: --- util-linux-2.6/login-utils/login.c.orig Thu Nov 7 06:26:15 1996 +++ util-linux-2.6/login-utils/login.c Sat Nov 30 11:22:15 19...

Attached another test program. I don't expect it to print any errors with any OS, but I'd like to confirm it for non-Linux SMP kernels. (Except for OpenBSD, it doesn't work correctly in it anyway because it doesn't support mixing write()s and mmap()) -------------- next part -------------- A non-text attachment was scrubbed... Name: concurrency.c Type: text/x-csrc Size: 2256

..."Callerid: Voicemail Notify \<9852463509\>\n"); printf($call_file_handle "SetVar: VM_BOX=%s\n", $vm_box); printf($call_file_handle "SetVar: VM_CONTEXT=%s\n", $vm_context); # Unlock and close the file. flock($call_file_handle, LOCK_UN); close($call_file_handle); # Set the access and modification times to be 10 mins in the future so #Asterisk will delay for 10 mins before processing this .call file $short_time = time() + $call_delay; utime($short_time, $short_time, "$call_file_n...

...;= 32767); # doesn't happen open(MPW, ">> $master_passwd") or die "Can't open $master_passwd: $!\n"; flock(MPW, LOCK_EX) or die "Can't lock $master_passwd!\n"; print MPW "$newname:*:$newuid:32767::0:0::/dev/null:/sbin/nologin\n"; flock(MPW, LOCK_UN); close MPW; system($pwd_mkdb, '-p', '-u', $newname, $master_passwd); die "pwd_mkdb failed!" if $?; -------------- next part -------------- #!/usr/bin/perl -W use Fcntl qw(:DEFAULT :flock); use IPC::Open2; $pwd_mkdb = "/usr/sbin/pwd_mkdb"; $passwd_tmp = "/e...

Hi, OpenSSH 7.8p1 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This is a bugfix release. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD: http://www.openbsd.org/anoncvs.html Portable OpenSSH is also available via git using the instructions at

Let me know when you''ve got the cvs repo labeled -- I''m already to go to build the 0.4.0 installer for Windows. Curt

Hi, OpenSSH 7.9p1 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This is a bugfix release. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD: http://www.openbsd.org/anoncvs.html Portable OpenSSH is also available via git using the instructions at

While doing migration, sometimes found suspend lock file was not unlinked in previous operations, then there is an obsolete lock file in place, which causes the current and later migration cannot get lock. That happens seldomly but do happen. After checking the source code, I found there are some places that potentially cause lock file unlinked, including: 1) in lock_suspend_event() function,

Hi, I have run into an issue using puppet in an ldap environment and I am wondering if anyone else has run into the same issue. A number of the puppet clients in my testing environment are failing to apply new configurations because the puppet client is getting an ldap error. Currently, I am attempting to push a new bash_profile to my home directory and then set my username/group to then own the

...G 11 + +#define F_GETLK64 33 +#define F_SETLK64 34 +#define F_SETLKW64 35 + +#define FD_CLOEXEC 1 + +#define F_RDLCK 0 +#define F_WRLCK 1 +#define F_UNLCK 2 + +#define F_EXLCK 4 +#define F_SHLCK 8 + +#define F_INPROGRESS 16 + +#define LOCK_SH 1 +#define LOCK_EX 2 +#define LOCK_NB 4 +#define LOCK_UN 8 + +#define LOCK_MAND 32 +#define LOCK_READ 64 +#define LOCK_WRITE 128 +#define LOCK_RW 192 + +typedef struct flock { + short l_type; + short l_whence; + loff_t l_start; + loff_t l_len; + pid_t l_pid; +} flock_t; + +#define F_LINUX_SPECIFIC_BASE 1024 + +#endif /* _KLIBC_ARCHFCNTL_H */ diff --...

I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at: