Archive for the ‘bug tracking system’ Category
April 11th, 2010 | 
Author: 
BMW Eavesdropping Device Spy Audio Bug with GSM Mobile Phone SIM Card Slot
http://popbuying.com/detail.pb/sku.Romisen_RC_R4_LED_Flashlight_Black_-28791
Brand New Eavesdropping Device with GSM Mobile Phone SIM Card Slot
Compact and portable handheld design
Easy to use and no any installation or setup needed
It work also work even you call this device oversea
Once you call this number, this device will auto answer
It is working like a phone with auto answer without speaker.
Eavesdropping Device built-in rechargeable battery
All GSM SIM card compatible
Feature tracking your mobile phone SIM system
You can actually hear anyones talking about you or whatever when you call in that sim cards phone.
Features a unique super- slim design, place it at home or even in the office
Eavesdropping area around 5 Meters
Come with USB cable, AC charger adapter and Packing box
Duration : 0:1:16
MEDICAL CORRUPTION,, INSURANCE CORPORATION,, GOVERNMENT CONTROL OVER YOU FORTKNOX
This is the only chance that you have. You have to stand up for yourselves now.
This is the will of God. Things are getting worse, and everything is almost all out of your control. You have to do something. Now, for the time being we still have the internet, that we can voice our concerns, but this is not going to last forever. Already, microsoft, is trying to buy a search engine, and then forget it, you could lose free access to the internet. Right, now, you have lost the electronics, control. ALL, techinicians, compromised the laptops, that I have bought. I possibly bought 30 laptops, all excellent machines but, I could not use them because they were completely controlled, by a third partition. ALL STORES. And, they are closely watched. They say, it is because of terrorism, but it is not. It is to protect the corruption of the medical system, and also the insurance companies. ALL CELLULAR phones that I purchased were compromised. I bought an Iphone, an expensive Nokia, and a Treo. Nothing works. I bought possibly over a 50 sim cards and none of them work. The seller, would record the sim card that I was buying, and as soon as I got to the hotel, it was cancelled. Or, if I was lucky enough, to have time on it, they would let me use it for a very short, time, then shut it down. So, what I started doing, is asking to look at the sim card, handed to me by the seller, then putting it into my pocket, so they could not record it. Then I would have a sim card for a little while. But, then I used my visa card, to put more time on it, and then it was shut down. So, now, they sell me all sim cards, because they record them ahead of time, and there is no time on them, and when I get to the hotel, it is shut down. It has been impossible for me to have a working cellular, for the past 12 months. With all of this equipment, I do not have a working cellular phone. Matters are getting so much worse. So much very worse. You have to wake up and stand up for yourself. This is the will of God or he will shut down this world. London England, they have cctv cameras, everywhere. In a city bus, there are 10 cameras. Ten. That is so very much. In all restaurants you will find these cctv cameras. There is no privacy. You are completely controlled.else, to monitor, the population. All of us. This terrorism, is hogwash. It is bullshit. Their agenda, is more sinister. Money, Greed Power. Take my town. This is a northern town, near the great north. I feel, that the car accident, that I went through was deliberate, to increase the public purse. The previous accountant, to me, in this town, also had an accident. He drowned. This man, was of the same caliber of work as myself. Now, in this town you have two bookkeepers left, and one large accounting firm. The bookkeepers, do not have the tax planing in their work. The large accounting firm francise, will not interview, their clients. How can you prepare a proper tax return if you do not speak to the client. Many deductions were missed. But, by my being so thorough, I was costing the city money. I feel I was targeted and more then once.
Laptops. They are compromised. The only way, that you can see the hacker is by buying the software ranish off ebay. The average person buying a laptop, will not, be able to know, that it has been compromised. Hacker can read, all letters, in any software. They can change all software, and rewrite it, as you are shutting and starting up the machine. They have taken my life completely. The land line telephones, are listened to. This from a distance. . 1995 I was so upset, I was spitting, fire. I put all my xrays, in the closet, and tried to organize my files. Then, I noticed, that one xray was missing. There is no way, that they knew where I had put this, unless, they could see in this room. I found the bug. It is a simple lightbulb, that is a camera, and can be installed in a matter of a few seconds. I found it with an RF device, tracker. This same type of device is under my skin. Now, you cannot have more control than this. They have installed a tracking device right under my skin, under my hair. I have tried to find it, and have not been successful. But, I do have the area where they entered to go under the skin. They have an obsession, and strong disease, that they have to control you.Please please do not take this lightly. This is very serious. THERE IS NO FREEDOM IN THESE DEMOCRATIC COUNTRIES. NONE. WHY, BECAUSE THEY ARE ROBBING YOU BLIND OF YOUR LIFE AND ANYTHING ELSE THEY FEEL LIKE IT. THEY MAKE THE RULES, THAT YOU FOLLOW. THIS IS YOUR LAST CHANCE TO STAND BY ME, AND FOLLOW GODS WILL. suzanne dubois stdubois@netzero.com page 3
Duration : 0:0:13
Posted in bug tracking system | 
Tags: CONTROL, CORPORATE, CORRUPTION, FORTKNOX, INSURANCE, SDUBOIS, STRONGHOLD | 
4 Comments »
The Hollywood Spy shop is located at 5910 W Sunset Blvd in Hollywood California. This spy shop carries a variety of items, from security and surveillance equipment, to spy cameras and gadgets. We have security cameras, nanny cams, diversion safes, pepper spray, spy sunglasses, GPS tracking systems, wireless transmitters and receivers, CCTV equipment, listening devices, bug detectors, body cameras and so much more.
Our expert staff will gladly help you find whatever product you may need for any spy operation or security system you need to set up. We even have installers that will come to your home and set up a security system for you.
For more information please visit our store or call us at 323-962-1061.
Duration : 0:0:53
Posted in bug tracking system |
Tags: asianwolf, bodycam, boulevard, california, Camera, covert, dvr, electronics, gadget, hidden, hollywood, security, shop, Spy, sunset, Surveillance, wolfcom |
1 Comment »
http://packages.debian.org/sid/developers-reference – - source in order to get them to compile for their target architecture; that would be considered a source NMU rather than a binary-only NMU. As you can see, we don’t distinguish in terminology between porter NMUs and non-porter NMUs. Both classes of NMUs, source and binary-only, can be lumped under the term “NMU”. However, this often leads to confusion, since most people think “source NMU” when they think “NMU”. So it’s best to be careful: always use “binary NMU” or “binNMU” for binary-only NMUs. 5.12. Collaborative maintenance Collaborative maintenance is a term describing the sharing of Debian package maintenance duties by several people. This collaboration is almost always a good idea, since it generally results in higher quality and faster bug fix turnaround times. It is strongly recommended that packages with a priority of Standard or which are part of the base set have co-maintainers. Generally there is a primary maintainer and one or more co-maintainers. The primary maintainer is the person whose name is listed in the Maintainer field of the debian/control file. Co-maintainers are all the other maintainers, usually listed in the Uploaders field of the debian/control file. In its most basic form, the process of adding a new co-maintainer is quite easy: * Setup the co-maintainer with access to the sources you build the package from. Generally this implies you are using a network-capable version control system, such as CVS or Subversion. Alioth (see Section 4.12, Debian’s GForge installation: Alioth ) provides such tools, amongst others. * Add the co-maintainer’s correct maintainer name and address to the Uploaders field in the first paragraph of the debian/ control file. Uploaders: John Buzz [jbuzz@debian.org], Adam Rex [arex@debian.org] * Using the PTS (Section 4.10, The Package Tracking System ), the co-maintainers should subscribe themselves to the appropriate source package. Another form of collaborative maintenance is team maintenance, which is recommended if you maintain several packages with the same group of developers. In that case, the Maintainer and Uploaders field of each package must be managed with care. It isrecommended to choose between one of the two following schemes: 1. Put the team member mainly responsible for the package in the Maintainer field. In the Uploaders, put the mailing list address, and the team members who care for the package. 2. Put the mailing list address in the Maintainer field. In the Uploaders field, put the team members who care for the package. In this case, you must make sure the mailing list accept bug reports without any human interaction (like moderation for non-subscribers). In any case, it is a bad idea to automatically put all team members in the Uploaders field. It clutters the Developer’s Package Overview listing (see Section 4.11, Developer’s packages overview ) with packages one doesn’t really care for, and creates a false sense of good maintenance. 5.13. The testing distribution 5.13.1. Basics Packages are usually installed into the testing distribution after they have undergone some degree of testing in unstable. They must be in sync on all architectures and mustn’t have dependencies that make them uninstallable; they also have to have generally no known release-critical bugs at the time they’re installed into testing . This way, testing should always be close to being a release candidate. Please see below for details. 5.13.2. Updates from unstable The scripts that update the testing distribution are run twice each day, right after the installation of the updated packages; these scripts are called britney. They generate the Packages files for the testing distribution, but they do so in an intelligent manner; they try to avoid any inconsistency and to use only non-buggy packages. The inclusion of a package from unstable is conditional on the following: * The package must have been available in unstable for 2, 5 or 10 days, depending on the urgency (high, medium or low). Please note that the urgency is sticky, meaning that the highest urgency uploaded since the previous testing transition is taken into account. Those delays may be doubled during a freeze, or testing transitions may be switched off altogether; * It must not have new release-critical bugs (RC bugs affecting the version available in unstable, but not affecting the version in testing); * It must be available on all architectures on which it has previously been built in unstable. Section 4.9.2, The dak ls utility may be of interest to check that information; * It must not break any dependency of a package which is already available in testing; * The packages on which
Duration : 0:7:9
http://packages.debian.org/sid/developers-reference – - to the original filename. Note that you don’t need to depend on sharutils to get the uudecode program if you use perl’s pack function. The code could look like uuencode-file: perl -ne ‘print(pack “u”, $$_);’ $(file) ] $(file).uuencoded uudecode-file: perl -ne ‘print(unpack “u”, $$_);’ $(file).uuencoded ] $(file) Chapter**7.**Beyond Packaging Debian is about a lot more than just packaging software and maintaining those packages. This chapter contains information about ways, often really critical ways, to contribute to Debian beyond simply creating and maintaining packages. As a volunteer organization, Debian relies on the discretion of its members in choosing what they want to work on and in choosing the most critical thing to spend their time on. 7.1.**Bug reporting We encourage you to file bugs as you find them in Debian packages. In fact, Debian developers are often the first line testers. Finding and reporting bugs in other developers’ packages improves the quality of Debian. Read the instructions for reporting bugs in the Debian bug tracking system. Try to submit the bug from a normal user account at which you are likely to receive mail, so that people can reach you if they need further information about the bug. Do not submit bugs as root. You can use a tool like reportbug(1) to submit bugs. It can automate and generally ease the process. Make sure the bug is not already filed against a package. Each package has a bug list easily reachable at http:// bugs.debian.org/packagename Utilities like querybts( 1) can also provide you with this information (and reportbug will usually invoke querybts before sending, too). Try to direct your bugs to the proper location. When for example your bug is about a package which overwrites files from another package, check the bug lists for both of those packages in order to avoid filing duplicate bug reports. For extra credit, you can go through other packages, merging bugs which are reported more than once, or tagging bugs `fixed’ when they have already been fixed. Note that when you are neither the bug submitter nor the package maintainer, you should not actually close the bug (unless you secure permission fromthe maintainer). From time to time you may want to check what has been going on with the bug reports that you submitted. Take this opportunity to close those that you can’t reproduce anymore. To find out all the bugs you submitted, you just have to visit http:// bugs.debian.org/from:[your-email-addr]. 7.1.1.**Reporting lots of bugs at once (mass bug filing) Reporting a great number of bugs for the same problem on a great number of different packages *** i.e., more than 10 *** is a deprecated practice. Take all possible steps to avoid submitting bulk bugs at all. For instance, if checking for the problem can be automated, add a new check to lintian so that an error or warning is emitted. If you report more than 10 bugs on the same topic at once, it is recommended that you send a message to [ debian-devel@lists.debian.org] describing your intention before submitting the report, and mentioning the fact in the subject of your mail. This will allow other developers to verify that the bug is a real problem. In addition, it will help prevent a situation in which several maintainers start filing the same bug report simultaneously. Please use the programms dd-list and if appropriate whodepends (from the package devscripts) to generate a list of all affected packages, and include the output in your mail to [ debian-devel@lists.debian.org]. Note that when sending lots of bugs on the same subject, you should send the bug report to [maintonly@bugs.debian.org] so that the bug report is not forwarded to the bug distribution mailing list. 7.2.**Quality Assurance effort 7.2.1.**Daily work Even though there is a dedicated group of people for Quality Assurance, QA duties are not reserved solely for them. You can participate in this effort by keeping your packages as bug-free as possible, and as lintian-clean (see Section**A.2.1, ***lintian*** ) as possible. If you do not find that possible, then you should consider orphaning some of your packages (see Section**5.9.4, ***Orphaning a package* ** ). Alternatively, you may ask the help of other people in order to catch up with the backlog of bugs that you have (you can ask for help on [debian-qa@lists.debian.org] or [debian-devel@lists.debian.org]) . At the same time, you can look for co-maintainers (see Section**5.12, * **Collaborative maintenance*** ). 7.2.2.**Bug squashing parties From time to time the QA group organizes bug squashing parties to get rid of as many problems as possible. They are announced on [debian-devel-announce@ lists.debian.org] and the announcement explains which area will be the focus of the party: usually they focus on release critical bugs but it may happen
Duration : 0:7:29
http://packages.debian.org/sid/developers-reference – - 5.9.4. Orphaning a package If you can no longer maintain a package, you need to inform others, and see that the package is marked as orphaned. You should set the package maintainer to Debian QA Group [packages@qa.debian.org] and submit a bug report against the pseudo package wnpp. The bug report should be titled O: package — short description indicating that the package is now orphaned. The severity of the bug should be set to normal; if the package has a priority of standard or higher, it should be set to important. If you feel it’s necessary, send a copy to [ debian-devel@lists.debian.org] by putting the address in the X-Debbugs-CC: header of the message (no, don’t use CC:, because that way the message’s subject won’t indicate the bug number). If you just intend to give the package away, but you can keep maintainership for the moment, then you should instead submit a bug against wnpp and title it RFA: package — short description. RFA stands for Request For Adoption. More information is on the WNPP web pages. 5.9.5. Adopting a package A list of packages in need of a new maintainer is available in the Work-Needing and Prospective Packages list (WNPP). If you wish to take over maintenance of any of the packages listed in the WNPP, please take a look at the aforementioned page for information and procedures. It is not OK to simply take over a package that you feel is neglected — that would be package hijacking. You can, of course,contact the current maintainer and ask them if you may take over the package. If you have reason to believe a maintainer has gone AWOL (absent without leave), see Section 7.4, Dealing with inactive and/or unreachable maintainers . Generally, you may not take over the package without the assent of the current maintainer. Even if they ignore you, that is still not grounds to take over a package. Complaints about maintainers should be brought up on the developers’ mailing list. If the discussion doesn’t end with a positive conclusion, and the issue is of a technical nature, consider bringing it to the attention of the technical committee ( see the technical committee web page for more information). If you take over an old package, you probably want to be listed as the package’s official maintainer in the bug system. This will happen automatically once you upload a new version with an updated Maintainer: field, although it can take a few hours after the upload is done. If you do not expect to upload a new version for a while, you can use Section 4.10, The Package Tracking System to get the bug reports. However, make sure that the old maintainer has no problem with the fact that they will continue to receive the bugs during that time. 5.10. Porting and being ported Debian supports an ever-increasing number of architectures. Even if you are not a porter, and you don’t use any architecture but one, it is part of your duty as a maintainer to be aware of issues of portability. Therefore, even if you are not a porter, you should read most of this chapter. Porting is the act of building Debian packages for architectures that are different from the original architecture of the package maintainer’s binary package. It is a unique and essential activity. In fact, porters do most of the actual compiling of Debian packages. For instance, when a maintainer uploads a (portable) source packages with binaries for the i386 architecture, it will be built for each of the other architectures, amounting to 12 more builds. 5.10.1. Being kind to porters Porters have a difficult and unique task, since they are required to deal with a large volume of packages. Ideally, every source package should build right out of the box. Unfortunately, this is often not the case. This section contains a checklist of “gotchas” often committed by Debian maintainers — common problems which often stymie porters, and make their jobs unnecessarily difficult. The first and most important thing is to respond quickly to bug or issues raised by porters. Please treat porters with courtesy, as if they were in fact co-maintainers of your package (which, in a way, they are). Please be tolerant of succinct or even unclear bug reports; do your best to hunt down whatever the problem is. By far, most of the problems encountered by porters are caused by packaging bugs in the source packages. Here is a checklist of things you should check or be aware of. 1. Make sure that your Build-Depends and Build-Depends-Indep settings in debian/ control are set properly. The best way to validate this is to use the debootstrap package to create an unstable chroot environment (see Section A.4.2, debootstrap ). Within that chrooted environment, install the build-essential package and any package dependencies mentioned in Build-Depends
Duration : 0:7:14
Army docs to help you evade, track and countertrack. Hey YouTube keeps pulling my links to these docs so if you want them you will have to pm an email I can send them to for you.
Duration : 0:9:40
Posted in bug tracking system |
Tags: air, army, bug, Force, marines, navy, out, tracking |
25 Comments »
Jesse Lindmar, Assistant Director of Computer Forensics for Sensei Enterprises, Inc. answers the frequently asked question, can you retrieve the data in a GPS or GPS tracking device? Beware even using a tracking device has its legal pitfalls. To learn more, watch the video then call Sensei at 703-359-0700.
Duration : 0:1:29
http://packages.debian.org/sid/developers-reference – - key, the Keyring Maintainers might reject the new key. Details can be found at http: //keyring.debian.org/ replacing_keys.html. The same key extraction routines discussed in Section 2.3, Registering as a Debian developer apply. You can find a more in-depth discussion of Debian key maintenance in the documentation of the debian-keyring package. 3.3. Voting Even though Debian isn’t really a democracy, we use a democratic process to elect our leaders and to approve general resolutions. These procedures are defined by the Debian Constitution. Other than the yearly leader election, votes are not routinely held, and they are not undertaken lightly. Each proposal is first discussed on the [debian-vote@lists.debian.org] mailing list and it requires several endorsements before the project secretary starts the voting procedure. You don’t have to track the pre-vote discussions, as the secretary will issue several calls for votes on [ debian-devel-announce@ lists.debian.org] (and all developers are expected to be subscribed to that list). Democracy doesn’t work well if people don’t take part in the vote, which is why we encourage all developers to vote. Voting is conducted via GPG-signed/encrypted email messages. The list of all proposals (past and current) is available on the Debian Voting Information page, along with information on how to make, second and vote on proposals. 3.4. Going on vacation gracefullyIt is common for developers to have periods of absence, whether those are planned vacations or simply being buried in other work. The important thing to notice is that other developers need to know that you’re on vacation so that they can do whatever is needed if a problem occurs with your packages or other duties in the project. Usually this means that other developers are allowed to NMU (see Section 5.11, Non-Maintainer Uploads (NMUs) ) your package if a big problem (release critical bug, security update, etc.) occurs while you’re on vacation. Sometimes it’s nothing as critical as that, but it’s still appropriate to let others know that you’re unavailable. In order to inform the other developers, there are two thingsthat you should do. First send a mail to [ debian-private@lists.debian.org] with [VAC] prepended to the subject of your message^[ 2] and state the period of time when you will be on vacation. You can also give some special instructions on what to do if a problem occurs. The other thing to do is to mark yourself as on vacation in the Debian developers’ LDAP database (this information is only accessible to Debian developers). Don’t forget to remove the on vacation flag when you come back! Ideally, you should sign up at the GPG coordination site when booking a holiday and check if anyone there is looking for signing. This is especially important when people go to exotic places where we don’t have any developers yet but where there are people who are interested in applying. 3.5. Coordination with upstream developers A big part of your job as Debian maintainer will be to stay in contact with the upstream developers. Debian users will sometimes report bugs that are not specific to Debian to our bug tracking system. You have to forward these bug reports to the upstream developers so that they can be fixed in a future upstream release. While it’s not your job to fix non-Debian specific bugs, you may freely do so if you’re able. When you make such fixes, be sure to pass them on to the upstream maintainers as well. Debian users and developers will sometimes submit patches to fix upstream bugs — you should evaluate and forward these patches upstream. If you need to modify the upstream sources in order to build a policy compliant package, then you should propose a nice fix to the upstream developers which can be included there, so that you won’t have to modify the sources of the next upstream version. Whatever changes you need, always try not to fork from the upstream sources. 3.6. Managing release-critical bugs Generally you should deal with bug reports on your packages as described in Section 5.8, Handling bugs . However, there’s a special category of bugs that you need to take care of — the so-called release-critical bugs (RC bugs). All bug reports that have severity critical, grave or serious are considered to have an impact on whether the package can be released in the next stable release of Debian. These bugs can delay the Debian release and/or can justify the removal of a package at freeze time. That’s why these bugs need to be corrected as quickly as possible. Developers who are part of the Quality Assurance group are following all such bugs, and trying to help whenever possible. If, for any reason, you aren’t able fix an RC bug in a package of yours within 2 weeks, you should either ask for help by sending a mail to the
Duration : 0:7:13
Here is a robot that my friend Adam and I built for a science fair. It is a miniature robotic tracking mount. The system consists of a 2DOF gimbal, 4 IR sensors and 2 servos to actuate the gimbals. The idea was that we are too lazy to actually properly position a solar panel, so, why not have it orient itself?
The sun moves through the sky, east to west, and depending on your position on the earth, and the time of year, the sun’s position in the sky is different as well. This robot can compensate for that. It moves twitchy because it was calibrated to move a solar panel, which we had removed so we could film the mechanics.
Duration : 0:2:0
Posted in bug tracking system |
Tags: 2DOF, BEAM, bug bot, electronics, heads, junkbot, robotics, Robots, solar, solar panel, solar tracker, tracker |
3 Comments »