search for: secret1

...the boxes. Does anyone see it? ------config files start------ site-0 ------ voip:etc/asterisk# more iax.conf [general] bindport=4569 bindaddr=192.168.3.60 bandwidth=low permit=192.168.3.205 ;register => user0:secret0@192.168.3.205 [site1] type=friend host=192.168.3.205 username=user1 secret=secret1 auth=md5 context=incoming trunk=yes qualify=1000 disallow=all allow=ilbc voip:/etc/asterisk# more extensions.conf [general] static=yes writeprotect=no [globals] ; Global Variables ; Internal SIP Phone Numbers PHONE1=SIP/2001 ; Other Site Authentication SITE1=IAX2/user1:secret1@site1 ; MACRO SEC...

On Thu, 26 Feb 2015, Damien Miller wrote: > > Yes I saw that later. > > > > The testsuite build fails on Solaris 2.6 thusly: > [...] > > regress/netcat.c:1037: error: 'struct msghdr' has no member named > > 'msg_control' > > ah, looks like we need to copy some bits from monitor_fdpass.c Perhaps like this: diff --git regress/netcat.c

...are being "authenticated". This seems to work : (...) secrets file = /etc/rsyncd/secrets1.inc &include = /etc/rsyncd/mymodules1/ secrets file = /etc/rsyncd/secrets2.inc &include = /etc/rsyncd/mymodules2/ (...) ie. any modules declared in mymodules1/ will use users/passwords in secret1.inc whereas mymodules2/ modules will use secret2.inc. is it the right way to implement this ? sorry if the question has been asked before thanks Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20130930/9702...

Hi, I had the following odd behaviour in Asterisk 1.2 - We are migrating to 1.6, and I will re-test ASAP, though it is quite hard to replicate, but I am curious to know whether it is a known IAX issue in 1.2. We had 2 users in iax.conf: [user1] username=user1 secret=secret1 context=context1 host=iax.hostname.com [user2] username=user2 secret= context=context2 host=dynamic deny=0.0.0.0/0.0.0.0 allow=1.2.3.0/255.255.255.0 A call came in with username=user2, the call was from the valid IP range specified in [user2], and the IAX debug trace showed the call as UNAUTHENT...

Hi, I tried to configure the new idmap interface. Currently without much success. I have two samba domains, trusting each other. Each PDC using it's own LDAP server. I tried idmap domains = DOM1, DOM2 idmap config DOM1:default = yes idmap config DOM1:backend = ldap idmap config DOM1:ldap_base_dn = ou=Idmap,dc=dom1,dc=mydomain,dc=de idmap config

...invalidcalls ;This account is used for inbound and outbound calls register => myuser:mypass@mydomain/999 [mydomain] type=peer host=myproxy context=sip username=myuser secret=mypass fromuser=myuser fromdomain=mydomain [user1] type=friend host=dynamic defaultip=default.IP username=user1 secret=secret1 dtmfmode=rfc2833 context=users callerid="User 1" nat=yes Here is part of the content of extensions.conf. ;This part is working fine [sip] exten => 999,1,Dial(SIP/user1,,tr) [users] exten => _8.,1,Dial,SIP/${EXTEN-1}@mydomain,tr When I dial the number 812345 from my SIP Pho...

....0/0 ACL localhost 127.0.0.1/32 ACL webinterface 192.168.0.2/32 ACL slave 192.168.50.22/32 ACCEPT localhost ACCEPT webinterface ACCEPT slave REJECT all and in upsd.users: [monmaster] password = secret0 allowfrom = localhost upsmon master [monslave] password = secret1 allowfrom = slave upsmon slave [admin] password = secret2 actions = SET instcmds = ALL allowfrom = webinterface Although upsd runs in a secured, private network, I would like to restrict the access. However, after upgrading from Debian lenny...

I have an strange issue with ldap passwd sync = only on FreeBSD 6.1 with Samba 3.0.25a + OpenLDAP 2.3.37 I have the OpenLDAP smbk5pwd overlay which successfuly synchronizes LM and NT passwords: $ ldappasswd -D 'cn=sambamgr,ou=managers,o=stars' -w sambapass -s secret1 'uid=lacoste,ou=Users,ou=Accounts,o=stars' Result: Success (0) My OpenLDAP auditlog file confirms that smbk5pwd is working: # modify 1187006837 o=stars cn=sambamgr,ou=Managers,o=stars dn: uid=lacoste,ou=Users,ou=Accounts,o=stars changetype: modify replace: userPassword userPassword:: e1NT...

...f ! cmp $OBJ/$t-tmp $exp > /dev/null 2>&1; then +?? ??? ?fail "ssh-keygen -yv output is not the expected value for $t-key" +?? ??? ?diff $exp $OBJ/$t-tmp +?? ?fi +?? ?rm -f $OBJ/$t-pub $OBJ/$t-tmp $exp +} + +for fmt in '' PKCS8 PEM ; do +?? ?for secret in '' 'secret1'; do +?? ??? ?rounds_list="0" +?? ??? ?test -n "$secret" -a -z "$fmt" && rounds_list="2 16" +?? ??? ?for rounds in $rounds_list; do +?? ??? ??? ?for t in $SSH_KEYTYPES; do +?? ??? ??? ??? ?trace "generating $t key in '$fmt' format wit...

...estsuite I see ssh-keygen dumps core in keygen-change.sh but all tests before that passes. $ gdb ssh-keygen GNU gdb (GDB) 7.8 ... Reading symbols from ssh-keygen...done. (gdb) core regress/core [New LWP 1] Core was generated by `/export/home/tgc/buildpkg/openssh/src/openssh-git/ssh-keygen -p -P secret1 -N 2'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xfedb4b14 in strlen () from /usr/lib/libc.so.1 (gdb) bt #0 0xfedb4b14 in strlen () from /usr/lib/libc.so.1 #1 0xfee07a20 in _doprnt () from /usr/lib/libc.so.1 #2 0xfee095e0 in printf () from /usr/lib/libc.so.1 #3 0x0005...

Hi Le 17/04/2020 ? 05:52, Damien Miller a ?crit?: > On Wed, 15 Apr 2020, Lo?c wrote: > >> Hello, >> >> In one recent change >> (https://anongit.mindrot.org/openssh.git/commit/?id=2b13d3934d5803703c04803ca3a93078ecb5b715), >> I noticed a regression. >> >> If ssh-keygen is given a private file without passphrase and without the >> corresponding

On Tue, 24 Feb 2015, Tom G. Christensen wrote: > I've switched to HEAD in the git repo and it now builds on Solaris > 2.6, 7, 8 and 9 but the testsuite still cannot be built due to the > missing <err.h>. > > I noticed one of the changes was about HOST_NAME_MAX but I don't > think that change addresses the real issue on at least these old > Solaris systems. It

I am configuring an asterisk server and I want to test the incoming configuration with my FXS handsets. I have the FXS lines able to call eachother and they can connect out the FXO lines. I changed the context for the FXS lines to "incoming" so that they would be able to test the setup for incoming calls. For the incoming context I have: [incoming] exten => s,1,Wait(1) exten