search for: tempest

...195.28.109.40 (S) Symmetric Unavail OK (1 ms) 1 dundi peers [1 online, 0 offline, 0 unmonitored] lk107*CLI> here is the dundi.conf of the first one: .... priv => local1,0,IAX2,priv:${SECRET}@${IPADDR}/${NUMBER},nopartial .... [00:11:43:3d:69:e6] model = symmetric host = lk107.tempest.sk inkey = lk107.tempest.sk outkey = lk40.tempest.sk include = priv permit = priv qualify = yes order = primary and the second one: .... priv => local1,0,IAX2,priv:${SECRET}@${IPADDR}/${NUMBER},nopartial .... [00:02:1e:f2:25:79] model = symmetric host = lk40.tempest.sk inkey = lk40.tempest.sk...

Hi, yes, it is. Anyway, below are some of the diagnostics I have tried. Linux box Win95 Box ========= =========== hostname: saturn tempest ip: 192.168.0.2 192.168.0.1 Below are the diagnostics that I have tried and I ahve logged them: 1. From win95 (tempest): ----------------------- c:\ping saturn Pinging saturn.tm.net.my [192.168.0.2] with 32 bytes of data: Reply from 192.168.0.2: bytes=32...

Folks, I have a Xen Asterisk VM with a TDM400 card. When I try to run dahdi_cfg, I get: tempest:~# dahdi_cfg -vvv DAHDI Tools Version - 2.2.0 DAHDI Version: 2.2.0 Echo Canceller(s): Configuration ====================== Channel map: Channel 01: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 01) Channel 03: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 03) Channel 04: FXS...

John R Pierce wrote: > wait. would deleting the inode /sys/(whatever) actually modify UEFI > memory? sure, writing to those inodes could do all sorts of harm, but > deleting the inodes in the /sys filesystem, I'm not so sure this isn't a > tempest in a teapot so to speak. It's going to get /boot. And under there, it'll get /boot/EFI. mark

...solve the following: Once a user authenticates themself to sshd, sshd among other things records the login in the wtmp, which `last` reads. However, sshd logs hostnames which are longer than 16 characters instead of IPs like normal programs would. As a result, I have useless entries such as: tempest ttyp4 1cust126.tnt5.ta Sat Mar 11 22:33 - 14:03 (15:29) which there is no way of telling what IP that was from. One option I found using was the UseLogin option, where openssh authenticates via login(1). This would work correctly but the wtmp logging was awkward: tempest tt...

...y run" on the guest. This runs the sysprep operation, but throws away any changes to the disk at the end. +=item B<--echo-keys> + +When prompting for keys and passphrases, virt-customize normally turns +echoing off so you cannot see what you are typing. If you are not +worried about Tempest attacks and there is no one else in the room +you can specify this flag to see what you are typing. + =item B<--format> raw|qcow2|.. =item B<--format> auto @@ -131,6 +138,11 @@ If you have untrusted raw-format guest disk images, you should use this option to specify the disk format...

Hi All, I am using CentOS 5.4 (Old-Out-Of-Date) and $ rpm -qa samba\* samba-client-3.0.33-3.15.el5_4.1 samba-common-3.0.33-3.15.el5_4.1 samba-3.0.33-3.15.el5_4.1 On Thursday, at a customer's site, I did my CentOS updates and got the above sort-of-new version of Samba. Problem: when CentOS booted back up, suddenly the only thing anyone could get into was their "homes" share. If

When i use openssh's UseLogin option (i.e. set it to "Yes").. i get duplicate entries in the wtmp file (when i type 'last' it displays users who logged on via sshd twice), like this: tempest ttyp4 63.10.229.126 Sat Mar 11 22:33 - 14:03 (15:29) tempest ttyp4 1cust126.tnt5.ta Sat Mar 11 22:33 still logged in note however that this is AFTER a user has logged off. It shows how long the user was logged on in the first entry (the one by login(1)) and correctly...

...) at io.c(189) I am running Suse 9.0 and rsync 2.6.0 on an AMD-K6-2/450 (192MB RAM, 400MB swap). I ran fsck on the source and destination partitions (ext3), and both are error-free. Can anyone shed some light on what is going wrong? Thanks. -- Ray Lischner, author of C++ in a Nutshell http://www.tempest-sw.com/cpp

...or I must download the source code of 2.2.6 to get this feature? Thank you very much, ===== Alceu Rodrigues de Freitas Junior -------------------------------------- glasswalk3r@yahoo.com.br http://www.imortais.cjb.net -- Hell is empty and all the devils are here. -- Wm. Shakespeare, "The Tempest" _______________________________________________________________________ Yahoo! GeoCities Tudo para criar o seu site: ferramentas f?ceis de usar, espa?o de sobra e acess?rios. http://br.geocities.yahoo.com/

I've googled my heart out, but I cannot see an example of ssh authentication with Active Directory and winbindd, particularly on Solaris 10. I have it working on Solaris 8 with telnet, but I'm trying to break my users of telnet. Has anyone got it working? If so, would you be willing to share the global section of your smb.conf and pam.conf with me? Is there something I need to put in one

...se I bethought myself that I could copy the function vecnorm from splus to my code. Then I was sad again because R complained > vecnorm(v) Error in .Fortran("d2norm", as.integer(length(x)), as.double(x), value = double(1)) : C/Fortran function name not in load table So, after this tempest of emotion, the question still remains: does R have this function under another name, or was it simply overlooked? Best regards, Faheem Mitha. -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.t...

http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz.sig Instead of having "Should v1.0 be released already" discussion, how about having "What's still missing from wiki.dovecot.org and how could it be improved" discussion? And what should the wiki exported to doc/ directory in the tarball look like? * If time moves

http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz.sig Instead of having "Should v1.0 be released already" discussion, how about having "What's still missing from wiki.dovecot.org and how could it be improved" discussion? And what should the wiki exported to doc/ directory in the tarball look like? * If time moves

Hi list, i have seen a lot of questions about VT-d on recent intel mobos. however, it seems that all tests are done on the newer socket 775-based xeon''s or core2''s, and not the 5000 series (socket 771 based). i was planning on getting a intel S5000V chipset, but found out that it does not support VT-d. Can anyone confirm a mobo that has this enabled and also has 2x LGA771

...created during conversion. This option is only used for debugging virt-v2v and may be removed in a future version. +=item B<--echo-keys> + +When prompting for keys and passphrases, virt-v2v normally turns +echoing off so you cannot see what you are typing. If you are not +worried about Tempest attacks and there is no one else in the room you +can specify this flag to see what you are typing. + +Note this options only applies to keys and passphrases for encrypted +devices and partitions, not for passwords used to connect to remote +servers. + =item B<-i> B<disk> Set the in...

Hi, this series refactors some guestfish code (not much), and exposes it via Common_utils, so it is possible to decrypt LUKS partitions when using virt-customize, virt-get-kernel, virt-sparsify, and virt-sysprep. This brings them closer in features with C tools. Most probably a couple more of other OCaml-based tools (virt-v2v to convert encrypted guests, and virt-builder to use encrypted

On Mon, February 1, 2016 1:56 pm, Valeri Galtsev wrote: > > On Mon, February 1, 2016 1:33 pm, m.roth at 5-cent.us wrote: >> Excerpt: >> Running rm -rf / on any UEFI Linux distribution can potentially >> perma-brick your system. > > Yes, I kind of like "rm -rf /". If my memory doesn't fail me, long ago it > was one of the tricky questions in sysadmin

I think it well to recall that the change which instigated this tempest was not to the network operations of a RHEL based system but to the 'INSTALLER' process, Anaconda. Now, I might be off base on this but really, ask yourself: Who exactly uses an installer program? And what is the threat model being addressed by requiring that the installer set a suitably...

...hanges to the distribution that directly affect users and users' expectations be more widely announced, and something like a request for comment be made for the proposed change, with replies to be sent to the -devel list. While I consider the very specific issue of the ISO naming to be a tempest in a teacup, I also appreciate the fact that mine is not the only opinion. But I believe that we would experience heavy turnover in such a go-between position as you describe.