similar to: OpenUsePrivilegeSeparation on Compaq V5.1A with C2/SIA Security

Hi Paul, your suggestion about batch.c got by the compiler without a peep and it got much farther along again with complaint from cc until.... [root@hyperion: rsync-2.5.4]#CC=cc; export CC; ./configure configure: Configuring rsync 2.5.4 checking build system type... alphaev5-dec-osf5.1 checking host system type... alphaev5-dec-osf5.1 checking target system type... alphaev5-dec-osf5.1 checking for

Greetings, here is the output of the 'configure' step and the compile step (using the Compaq cc compiler that comes with Tru64 V5.1A. The configure reported success and most of the compile steps cam through error/warning free except for the one that stumbled. Can someone help me out here? I am willing to provide a binary for Tru64 V5.1A if we can swat this bug. We depend greatly on Rsync

Hi, I have recently loaded Openssh 3.4p1 on an Tru64 Unix 5.1A system. I followed the installation instructions described in INSTALL, essentially using all default settings, and it went throught without any obvious errors. I can then use the root account to initiate outbound and inbound ssh calls, and can log on without any problems. The trouble is that when I try to use ssh to log in (from a

Something really hosed Digital/Tru64 UNIX SIA support in 2.5.2p1. I haven't been able to figure out what changed in the code, but the symptom seems to be that the TTY name being registered with SIA is truncated to eight characters. This apparently prevents it from matching with entries in the tty database, and the dreaded "Cannot obtain database information on this terminal

Hi, develop members: When I installed OpenSSH after reading the document INSTALL, I found one typo in this document. The configure option for OSF1's Security Integration Architecture is -ofssia, NOT -sia. The following is the patch for fixing this typo: ---(cut here)--- --- INSTALL.orig Thu Jul 25 13:36:25 2002 +++ INSTALL Wed May 21 06:21:12 2003 @@ -125,3 +125,3 @@ ---with-sia,

Hi All. There have recently (well, today :-) been changes to OpenSSH Portable's auth-passwd.c from OpenBSD to accomodate forced changes of expired passwords. (Rabid password expirers shoulon't get excited yet, it's currently bsdauth only, but support for other platforms should start trickling in shortly). As part of that, some individual platforms have gained their own

http://bugzilla.mindrot.org/show_bug.cgi?id=814 Summary: Turning on OSF SIA causes linker errors in sshd Product: Portable OpenSSH Version: -current Platform: All OS/Version: OSF/1 Status: NEW Severity: critical Priority: P1 Component: Build system AssignedTo: openssh-bugs at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=802 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |821 nThis| | Summary|sshd of openssh-3.8p1 |sshd configured with SIA

I have recently written a (minimal) Tru64 Unix SIA password module for Dovecot as part of testing a Dovecot installation. Has anyone else written a Tru64 Unix SIA module? Is anyone else interested in such a module? If so, how might I/we go about getting this/such a module into the main Dovecot source? Thanks -- Simon L Jackson Carringbush.Net +- Carringbush.Net Hosting * Development *

./configure --with-sia # ./dovecot --build-options Build options: ioloop=poll ipv6 openssl SQL drivers: Passdb: checkpassword passwd passwd-file Userdb: checkpassword passwd prefetch passwd-file static # ./dovecot --version 1.0.8 # ./dovecot -n # 1.0.8: /usr/local/etc/dovecot.conf protocols: pop3 listen: *:10100 ssl_disable: yes disable_plaintext_auth: no login_dir:

I have "PermitRootLogin no" in my sshd_config, but under Tru64 and SIA, the root login attempts still get passed to the SIA system (so I get lots of warnings about failed root logins). On systems with a "max failed attempts" setting, the root account can be locked out this way. I started looking at the code, and I'm not sure I understand what I see. In auth-passwd.c,

Regards to everyone, I'm trying to make freeBSD compliant with C2 (orange book C2). Is there any guide for freeBSD made for this porpouse or similar? Thanks to all of you, Rubén _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus

[PATCH 1/2] Support multiple C3 states. There may be multiple ACPI C3 states mapped into different CPU C-states.So made some modification to support this case. [PATCH 2/2] Handle C2 LAPIC timer & TSC stop. ACPI C2 is quite possible mapped to CPU C3 or deeper state, so thinking from worst cases, enable C3 like entry/exit handling for C2 by default. Option ''lapic_timer_c2_ok''

Current xen-linux (2.6.18) not include support for Cx MWAIT entry method. Back port from latest Linux kernel (already there since 2.6.23). Without this patch, _CST method couldn''t get C states with FFH address space type. Signed-off-by: Wei Gang <gang.wei@intel.com> Jimmy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Without this patch, while running on platforms on which the deepest C-state is C2, acpi_processor_idle fns will call into NULL function. BTW, made a little enhancement for keyhandler print-out to make it more readable. Signed-off-by: Wei Gang <gang.wei@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

ACPI C2 is quite possible mapped to CPU C3 or deeper state, so thinking from worst cases, enable C3 like entry/exit handling for C2 by default. Option ''lapic_timer_c2_ok'' can be used to select simple C2 entry/exit only if the user make sure that LAPIC tmr & TSC will not be stopped during C2. Signed-off-by: Wei Gang <gang.wei@intel.com>

On Mon, Dec 15, 2014 at 05:54:51PM +0000, Richard W.M. Jones wrote: > No idea why this happens: > > index-parse.y: In function 'yyparse': > index-parse.c:1256:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow] > if (yyss + yystacksize - 1 <= yyssp) > ^ > > It only happens on one machine,

hi all it seems like whatever I do, I can't use more than 1 BRI on my AVM C2 with chan_capi. Both channels seem to work, but not at the same time. And - yes - they're connected to different NT boxes :) Any ideas? kapejod? -- Roy Sigurd Karlsbakk, Datavaktmester ProntoTV AS - http://www.pronto.tv/ Tel: +47 9801 3356 Computers are like air conditioners. They stop working when you open

hi all I still can't use both BRIs on the AVM C2 with chan_capi. This is _annoying_ since people have started complaining about the number of available lines. Have anyone else seen this? thanks roy -- Roy Sigurd Karlsbakk, Datavaktmester ProntoTV AS - http://www.pronto.tv/ Tel: +47 9801 3356 Computers are like air conditioners. They stop working when you open Windows.

I have an asterisk installation connected to 2 isdn lines via an AVM C2 card. modules seems to load well, lsmod gives : c4 19588 4 b1 24192 1 c4 capidrv 28468 2 isdn 134604 9 capidrv slhc 7552 1 isdn capi 18112 4 capifs 6024 2 capi kernelcapi 46112 4