#using as reference & if i give it like 3 to 5 sec of full sensitivity from me i get bravely weepy. no part of that sentence is exaggerated | Explore Tumblr Posts and Blogs

user-name-not-found5 · 3 years

Text

Interrogation Techniques pt. 8

Whew! Sorry this has taken so long to update, I had to take a little break from social media. Anyway, I'm hoping to finish this up soon. Previous: 1, 2, 3, 4, 5 , 6, 7

Kylo Ren is determined to get the map out of the Resistance Pilot. By any. Means. Necessary.

Even if that means exploring new ways to sexually psychologically manipulate his victims into getting what he wants.

AU where the map leads to Luke’s new Jedi Temple, where he is training the next generation of Jedi. Poe is a Resistance pilot, who General Leia Organa has put in charge of running the transport routes in order to bring force-sensitive younglings to the temple where they belong. The First Order is headed by Kylo Ren, a fallen Jedi just as Count Dooku was, and he is determined to end the Jedi for good.

Warnings overall: non-con, torture, violence, manipulation, smut, absolutely filthy smut, degrading language, abuse

Warnings for this chapter: Mild violence/references to violence, references to killing of the younglings in the original prequels, villain is convinced he's the hero

BB-8 rolled down the corridors, occasionally stopping to consult the holo-map he’d pulled from the base systems. The trooper jogged beside him, wheezing through his helmet.

“Come… on…. man…” BB-8 stopped at a door port, letting the trooper catch his breath as he docked into the system. Hands on his knees, 2187 yanked his helmet off, tucking it under his arm. “You’re going to need.... A retinal… scan… to…” He held up a hand. “Gimme a sec…”

I’m not sending a comm outside the base. I’m sending one from inside.

The trooper sighed, running his hand over his face. “I don’t. Speak. Droid!”

Well, I don’t speak IDIOT.

The door whirred open, and BB slid inside, 2187 close behind. He quirked an eyebrow at the array of glowing panels and buttons, placing his hands on the center console. BB docked into another port, navigating slowly through the system until he found what he was looking for.

“Alright, you do your thing, we’ll get your pilot, and then we’re out of here, okay?” He paced, running his hands over his short-cropped hair. “Stars, let the Captain be on… I don’t know, a lunch break? Blaster-cleaning? Disciple row? Anything but patrol right now.”

A panel across the room began to hum, and BB rolled over to access the new port. He turned his head towards the trooper, giving his best attempt at a reassuring beep. The half-hearted smile he got in response was encouraging enough that he didn’t feel so guilty turning back to his work. The pair sat in silence for a bit, the soft whirring of machinery keeping them company before BB slid back with a triumphant little ditty.

“You got it?”

Hell-fucking-yeah I did!

The trooper’s comm beeped, and he clicked the speaker, letting the automated voice play out.

“Attention all base personnel. Please route around the detention corridor. A hazardous chemical spill has made the area unsuitable for transversal. Repeat. Route around the detention corridor.”

He raised an eyebrow at the droid. “For a little guy, you’re really scary, you know that?”

Thank me later. Let’s go get Poe.

Ren sat completely still, his legs crossed in front of him, his back perfectly straight as he inhaled, and exhaled again slowly. His mind floated out, spreading like a dark cloud. Something was catching his attention, something drifting closer, ever closer. Something strong, something… He stiffened. Her face formed in the cloud, the darkness draining and replaced by blinding light until she blinked into view. Her dark hair fell around her shoulders, brown eyes full of sadness.

“Ben.”

“You know that isn’t my name anymore.” His voice came out as a low hiss, eyes boring into her, willing her to go away.

Rey shook her head. “I will always look at you as the man who used to be my friend. Not the man you have become.”

“Then you are weak. Blinded by foolish attachments,” He sneered. “Your Master would be disappointed in you.”

He swallowed the lump in his throat as she flinched back, barely perceptible, but he knew her well. Too well… they’d grown up together, in the temple. She had been one of his closest friends, for so long…

“Ben,” Her voice was soft, coaxing. “I understand your anger. Your pain. Luke has made many mistakes, but he is only one man. He is haunted by a past that we may never understand. I’m sorry that he pushed you so far.”

He inhaled sharply. A bitter laugh slipped through his lips. “I thought you were more than this- his feeble messenger. Rey, a noble Jedi Knight, has been reduced to a mouthpiece for a corrupt, mad old man.” He shook his head. “You excuse his actions so easily- no matter his past, I trusted him. I needed him, I needed his guidance against the darkness,” His voice caught in his throat as the familiar roar of anger pressed in. “And he tried to murder me. His nephew.” His fists tightened. “Who’s to say he won’t try to kill you? Or follow in his father’s footsteps, and end the Jedi Order, bathing it in blood once again? It wasn’t the Clones that ended the next generation- it was my grandfather, from the inside.”

He was surprised when she nodded.

“You’re right, Ben. What he did, it was unforgivable. You needed him, you needed his confidence in you, you needed his trust. I’m sorry that he failed you. Which is why I won’t,” She brushed through the mists, and he could almost feel her hand on his skin back in his quarters. “I won’t fail. I will bring you back where you belong. Together, we can fix this. We can bring peace, Ben. Your anger has guided you this far, but where does it leave you?” She wrapped her arms around him gently. “You traded one Master for another.”

Ben snapped out of his meditation, sweat pooling on his back. She had seen so far into him, looked at his anger, and hatred, and hurt, and had still asked him to come home. Rey had always been good at that- they had a deep connection, growing up so close together. Hers had been the shoulder he cried on when he missed home, his was the shoulder she leaned on when a nightmare about the desert sands plagued her. She never spoke much of her past- he knew that in the power vacuum left after the Sith destroyed each other, several factions of the former Galactic empire vied for power. Many people had died, and the carnage had continued until he’d risen. He rolled his shoulders back. She spoke of bringing peace, and yet the Resistance was the source of the continued conflict. He had reunited the Empire, shaped and molded and forced it into the form of the First Order. He had ended the needless battles of factions, quelled the bloodshed, using force only when those little scraps had failed to recognize his new rule. He was the son of a Princess, he was well-versed in the lessons of diplomacy that she had vested to him; where his diplomacy failed, the anger of his Master’s betrayal fueled him into battle.

“I have brought peace,” The words slipped from his lips, hanging softly in the air. “The Jedi are meant to be peace-keepers. They should be on my side.”

But he was a tyrant. His hands curled into fists.

He had a map to follow.

Poe groaned. He was hanging from his wrists, held in suspension as energy surged around him, occasionally hitting him with a pulse that left him gasping for breath. He wasn’t sure when he’d last seen Ren- a few times, he’d passed out from the pain, or exhaustion, leaving him to wonder how many hours he’d lost to darkness. He was alone, at least. A few times, he’d woken to the stares of a few troopers, muttering orders to each other and adjusting the dials on the console. He was beginning to lose his resolve, as much as he hated to admit it. It would be nice, really, to just let go. Give the map up, and at least he could die. He snarled, fire surging in his gut. What was he thinking- he wouldn’t be the only one to die. These were children he was talking about, innocent kids, born with a power through no fault of their own. They needed the Jedi, needed that guidance, and he wasn’t going to let them suffer just because he was hurting. He jolted again as another surge crested through his body. He’d almost rather be under Ren again…

He shivered, despite himself. The aphrodisiac had a lingering effect, creeping into his dreams with memories of the heat in his belly, the leather glove clasped around his mouth, fingers curled in his hair. The way he’d shaken beneath him, the hot breath against his ear as he’d been fucked into a daze. He’d enjoyed it, and that thought disturbed him more than the idea of further torture.

The door slid open as another surge hit him, and he gasped, his back spasming at the pressure. Chest heaving, he jut his chin forward at the trooper who hovered in the doorway.

“Come to turn up the pressure again? Shame, I was getting a bit bored of this method.”

His eyes widened as the trooper leaned back into the hall, and waved someone forward, ducking into the room. Rather than head to the console, he waited by the door, until a small ball of energy rolled into the room. Poe laughed incredulously.

“BB-8?!”

Thank the stars! Master Poe!

BB-8 whirred happily, docking into a port. Poe dropped, the trooper catching him carefully in his arms, and helping him to his feet. He fixed him with a confused glance, flicking his gaze back and forth from the white helmet to BB.

“He a friendly?”

As far as I can tell. Looking for a pilot to get off this hellhole.

He arched an eyebrow, cocking his head at the trooper. “You a defector?”

The trooper was quiet for a second before pushing his helmet up, and setting it to the side. Poe’s eyes lingered on his face. He had wide, dark eyed, short-cropped dark hair, and full lips. He was handsome. He shook the thought, tacking it up to the last of the drugs.

“I’m not going to kill for them.” His voice was firm, but he spoke quietly. Poe just nodded, and let him help him hobble towards the door. BB picked up the rear, and the trio moved quickly down the hallway, to the hangar.

#poe dameron #poe dameron smut #canon offshoot #star wars #star wars smut #tros #darkpilot #tfa #tlj #reylo #finnpoe

5 notes · View notes

bloojayoolie · 5 years

Photo

Africa, Anaconda, and Bailey Jay: Outgoing, social, affectionate & very sweet. A sterling resume, a wonderful family pet Id 52882, 4 Yrs. 52 lbs. of Love, Spayed & Waiting for YOU, Manhattan ACC TO BE KILLED - 2/26/2019 Africa so adorable and she needs our help finding the right home <3 AFRICA’s intake photo doesn’t do her justice so we tried to get a screen capture off her adorable video with friend Don Draper. She’s incredibly beautiful, with a glossy, gleaming ebony coat and sparkling eyes. She looks to us to be a Labrador mix, and when she walks around in play yard, she literally prances like a pony, which caused us to burst out laughing. Outgoing, friendly, and very sweet, she is understandably a bit tense at the shelter with all the new people she is meeting. Her life, until now, was spent with her 2 parents, though they claimed she was found as a stray. We question every “stray” story we hear, here, at MLD, especially when a dog as magnificent as Africa is dropped off with glowing notes, a perfect and sterling resume of skills (housebroken, knows many commands, never guards her stuff, and likes to sleep in her dog bed). But whatever the reason for not wanting to care for this precious girl anymore, we would like to see her out of the shelter and into a home today. Please hurry and MESSAGE our page or email us at [email protected] if you can foster or beautiful Africa and give her back her life. A volunteer writes: Africa's soulful eyes look deep into your heart and ask only one question: Will you love me? She's a sweet velveteen beauty, shy at first but smart enough to know that hanging out with people means petting and treats and brave enough to approach whenever someone extends a hand in friendship. She always comes running when you call her, sits very politely for treats and was taught commands for stay and shake paw too. Toys are chased and then happily shared and in a home environment I bet she'll blossom into the same playful, highly active dog her former owner described. Africa greets other pups politely on leash or off, has lived with a small dog and is friendly toward her same size peers but mostly prefers nuzzling with human friends to roughhousing with the playgroup. Her favorite kind of petting is side rubs and if you appreciate a good 'leaner' as much as I do then she's definitely the gal for you! Africa is beautiful inside and out, a good girl ready to go home and enjoy some well-deserved TLC from a family as gentle and affectionate as she is. Will you be the one to love her forever? MY VIDEOS: Africa and Don Draper https://youtu.be/wCCWC3J5NXE Africa shows off her soft side <3 https://youtu.be/ktV1CiREjt0 AFRICA, ID # 52882, 4 Yrs. Old, 52.8 lbs. Manhattan ACC, Large Mixed Breed, Black, Spayed Female Owner Surrender Reason: Stray Shelter Assessment Rating: LEVEL 3 (Reference chart at bottom of post for Ratings information) Medical Behavior Rating: OWNER SURRENDER NOTES – BASIC INFORMATION: Africa is an approximately 4 Yr Old Large Mixed Breed Spayed dog. She previously lived with 2 adults. With strangers, Africa is outgoing and friendly. Africa has interacted with a small, old dog. The other dog was fearful of Africa and would retreat. Africa has no guarding issues. Africa has no bite history. She is housetrained and has a high level of energy – she is playful. Other Notes: Previous owner says 3 times a day, she give Afirca fresh water. Africa pulls hard on the leash. Africa pees on the grass. Africa knows how to sit, stay and give paw. Africa went to sleep on the dog bed. SHELTER ASSESSMENT: Date of assessment: 20-Jan-2019 Summaries: Leash Walking Strength and pulling: Moderate-hard Reactivity to humans: None Reactivity to dogs: None Leash walking comments: None Sociability Loose in room (15-20 seconds): Distracted, a bit fearful Call over: Approaches readily Sociability comments: Bit tense, approached with tail wagging but tense body Handling Soft handling: Tolerates contact Exuberant handling: Fearful Handling comments: Tense and pursed lips when her leg was touched Arousal Jog: Follows (low body) Arousal comments: None Knock: Tenses Knock Comments: Tense and hard stared during knock and when assistant walked in Toy: No response Toy comments: None PLAYGROUP NOTES – DOG TO DOG SUMMARIES: The previous owner of Africa reports interactions with an older fearful dog, without much detail. Africa has appeared fearful when introduced to other dogs in the care center, but has been tolerant of polite approach from respectful dogs. At this time, it is recommended Africa have slow introductions to dogs who are respectful and calm. 1/19: When introduced off leash to a male dog, Africa allows polite greeting but remains fearful and mostly avoids. 1/23: Africa allows polite greeting but mostly avoids the other dogs. 1/28 -29: Africa greets other calm dogs politely and mostly seeks attention from human handlers. INTAKE BEHAVIOR - Date of intake: 17-Jan-2019 Summary: Loose body for collaring, became tense when put in kennel/van, tail tucked, whale eyed MEDICAL BEHAVIOR - Date of initial: 20-Jan-2019 Summary: Very tense ENERGY LEVEL: Africa is described as having a very high level of activity. We recommend long-lasting chews, food puzzles, and hide-and-seek games, in additional to physical exercise, to positively direct her energy and enthusiasm. BEHAVIOR DETERMINATION: Level 3 Behavior Asilomar TM - Treatable-Manageable Recommendations: No children (under 13) Recommendations comments: No children: Due to the fearful behavior Africa has displayed at the care center (tensing, pursing lips, hard staring) we recommend an adult only home. Potential challenges: Handling/touch sensitivity, Fearful/potential for defensive aggression, Potential challenges comments: Africa tensed and pursed her lips when her leg was touched on her assessment. Please see handling on Handling/touch sensitivity. Africa has displayed very fearful behavior at the care center. Please see handout on Fearful/potential for defensive aggression. MEDICAL EXAM NOTES 5-Feb-2019 Progress Exam Hx: In foster care. Started coughing and sneezing about 3 days ago, and these symptoms have been increasing. Pt still energetic and eating well. S: Pulling on leash, jumping around, excited. Allows all handling, wagging tail, soft body. O: BAR-H, BCS 6/9, MMs pink and moist, CRT <2 sec EENT: Mild serous nasal discharge. Mild mucoid ocular discharge, erythematous conjunctiva. No discharge AU. Mild tartar and gingivitis. PLNs: Not significantly enlarged. H/L: NSR, NMA. Regular coughing. Panting. Normal resp effort. Difficult to auscult lung sounds due to coughing and panting. Abd: Soft, no pain on palpation, no masses palpated, not distended M/S/I: Amb x4. No skin lesions noted. UG: Female, small nipples and vulva, no discharge or masses. Neuro: Alert and appropriate, no sign neurological deficiencies A: 1. CIRDC; no sign of pneumonia 2. Slightly overweight Short-term prognosis: Good P: Canine infectious respiratory disease complex (CIRDC) is a term we use to describe an upper respiratory infection in a dog. At ACC we frequently see infections caused by a bacterium called Mycoplasma cynos. Sometimes there is a secondary viral infection as well. At ACC we treat CIRDC with an antibiotic to treat the bacterial component, but the virus just has to run its course, just like a head cold in a human. This may take 7-14 days. PLAN: Please give 2 tablets of doxycycline by mouth once daily for 14 days. The tablets are 100 mg tablets so that is a total of 200 mg per day. Additionally, please give 1.5 tablets of enrofloxacin (total of 204 mg) once daily for 14 days - this is another antibiotic - and 3/4 tab of Cerenia (total of 45 mg) once daily for 4 days - this is an anti-nausea medication. While your dog is sick, he or she may not want to eat because of the nasal discharge that makes it hard for him or her to smell the food. You can tempt your dog to eat with peanut butter, boiled chicken, plain ground hamburger, chicken broth on his or her regular food or other delicious items. Please seek veterinary care if your pet: a) is not â€œturning the cornerâ€ and starting to get better within 5 days b) is still sick and coughing in 2 weeks c) is extremely sick, weak, or not eating at any point and you are concerned 29-Jan-2019 Progress Exam Patient is still highly anxious, agitated and vocalising in kennel. A - High shelter anxiety P - Increase trazadone dose 10 mg/kg BID PO indefinitely 20-Jan-2019 DVM Intake Exam. Estimated age: 4-5 based on dentition. Microchip noted on Intake? N. Microchip Number (If Applicable): n. History : os. Subjective: BARH, Observed Behavior : very tense - for safety placed a muzzle and allowed for full PE. Evidence of Cruelty seen -n. Evidence of Trauma seen -n. Objective: T = -,P = wnl, R = wnl, BCS = 5/9. EENT: Eyes clear, ears clean, no nasal or ocular discharge noted. Oral Exam: muzzled - did not examine fully- mild calculus on the canines (1/5) otherwise teeth in good condition. PLN: No enlargements noted. H/L: NSR, NMA, CRT < 2, Lungs clear, eupnic. ABD: Non painful, no masses palpated. U/G: spay scar and tattoo - vulva unremarkable. MSI: Ambulatory x 4, skin free of parasites, no masses noted, healthy hair coat. CNS: Mentation appropriate - no signs of neurologic abnormalities. Rectal: externally normal. Assessment: Healthy. *** TO FOSTER OR ADOPT *** HOW TO RESERVE A “TO BE KILLED” DOG ONLINE (only for those who can get to the shelter IN PERSON to complete the adoption process, and only for the dogs on the list NOT marked New Hope Rescue Only). Follow our Step by Step directions below! *PLEASE NOTE – YOU MUST USE A PC OR TABLET – PHONE RESERVES WILL NOT WORK! ** STEP 1: CLICK ON THIS RESERVE LINK: https://newhope.shelterbuddy.com/Animal/List Step 2: Go to the red menu button on the top right corner, click register and fill in your info. Step 3: Go to your email and verify account \ Step 4: Go back to the website, click the menu button and view available dogs Step 5: Scroll to the animal you are interested and click reserve STEP 6 ( MOST IMPORTANT STEP ): GO TO THE MENU AGAIN AND VIEW YOUR CART. THE ANIMAL SHOULD NOW BE IN YOUR CART! Step 7: Fill in your credit card info and complete transaction HOW TO FOSTER OR ADOPT IF YOU *CANNOT* GET TO THE SHELTER IN PERSON, OR IF THE DOG IS NEW HOPE RESCUE ONLY! You must live within 3 – 4 hours of NY, NJ, PA, CT, RI, DE, MD, MA, NH, VT, ME or Norther VA. Please PM our page for assistance. You will need to fill out applications with a New Hope Rescue Partner to foster or adopt a dog on the To Be Killed list, including those labelled Rescue Only. Hurry please, time is short, and the Rescues need time to process the applications.

#funny #lol #humor #memes #meme #memehumor #dank memes #funny pics #rolf #lmao #Africa #Anaconda #and

1 note · View note

hnd1dmonikaszepielamajorke-blog · 5 years

Text

ILLUMINATE

During my research to this project, I came across LLAP(Light Art Performance Photography) it is a duo Jan Leonard Woeller and Joerg Miedza. Their technique differs slightly from standard light painting in that the camera is capturing the light performance. They create such good work that their projects are sponsored by Canon, Zeiss and Led Lenser. They worked with Nike in 2010 to create an ad for the World Cup.

Technique

- long time exposures

- moving light sources used to create luminous light sculptures

- one composition includes 1-20 steps during one exposure what demands body control to achieve the desired effect

- no Photoshop manipulation

Equipment

- 12.8-megapixel EOS 5D DSLR or 21.1-megapixel EOS 5D MARK II(allows print large formats); both of these cameras capture long exposures with very little or no visible noise

- very solid tripod

- remote control to trigger exposure(that often goes to 60 minutes!)

- a range of different light source: fireworks, light sticks, flash, specifically developed luminous tools

References:

https://petapixel.com/2013/08/27/10-amazing-light-painting-photographers/

https://allthatsinteresting.com/light-painting/2

http://lightpaintingphotography.com/light-painting-artist/featured-artist-2/lapp-pro/

https://cpn.canon-europe.com/content/interviews/light_art_performance_photography.do

Dean Chamberlain is the father of light painting photography. He was the first person who used the term “light painting”.He has created stunning portraits of well-known individuals such as David Bowie and Paul McCartney.His works have appeared in Vanity Fair and the Washington Post.

The photo above was taken like all others in complete darkness. The exposure time 3 hours(the exposure times vary between some minutes and some hours per sheet of film).Due to he uses a film camera he doesn’t use any Photoshop manipulations so all lights which we see were captured by the camera. He uses a different source of light like a torch for example. The model was sitting there for the whole time of exposure.

The image of the forest patch has a kind of light with I would like to recreate on my own image.

References:

http://lightpaintingphotography.com/light-painting-artist/featured-artist-2/dean-chamberlain/

https://petapixel.com/2013/08/27/10-amazing-light-painting-photographers/

Troy Paiva photographs abandon buildings and places that America has lost to time as he says.

Technique

All his photos were taken in full darkness, in- low or no-light condition, on or near the full moon what with the added light was the main source of light. Camera settings: ISO 100 or 200, at f/5.6 or f/8, exposure times 2-8 minutes, WB 3500-4000K or 5000-8000K; Cameras: Kodak160T(FILM CAMERA), Canon 20D and 60D DSLR with wide angle lenses

Lighting(all hand-held).He used one single source of light from several angles also snoots and gobos to manipulate the way the light falls.

- xenon and LED flashlight

- single Canon 430EX strobe mask with a theatrical gel material

- HSB- adjustable Protomachines Flashlight

Post-production

Lighting and color all done in camera. The contrast and perspective adjustment also lens flare clean up only made in Photoshop.

References:

http://lightpaintingphotography.com/light-painting-artist/featured-artist-2/troy-paiva/

https://lostamerica.com/technique/

Digital noise is the equivalent of film grain for the analog camera. For digital images, noise appears as random speckles and can degrade image quality. Noise increases with sensitivity settings in the camera, length of exposure, temperature and even vary amongst different camera models.

Types of noise

How to reduce the noise

1. Shoot at lower ISO- higher ISO settings tell your camera’s sensor to group pixels together to capture more light what makes an image look noisy. Use the widest shutter speed, tripod or flash for lower ISO

2. Shoot in Raw-Jpg files has already some noise, Raw files are more flexible in post-production to remove noise and increase exposure.

3. Be careful when doing long exposure - if the exposure is too long the sensor of the camera can begin to heat up and pixels will render incorrect colors and exposure

4. Use in-camera noise reduction- the function in a camera called High ISO noise reduction or Long Exposure Noise Reduction allows reducing noise after an image was shot. The camera analyzes the image and fixes pixels which are not properly rendered. It takes some time usually the same as long exposure was.

5. The noise might be reduced in post-production in Photoshop(Camera Raw-Noise Reduction) or in Lightroom.

References:

https://www.cambridgeincolour.com/tutorials/image-noise.htm

https://digital-photography-school.com/how-to-avoid-and-reduce-noise-in-your-images/

Planning

I am planning a shoot in the Pollock Park the fairy garden. At first, I thought about the portrait but then I realize that this location will give me a more interesting image. I would like to use single light from different angles or two sources of light with different color.

https://www.tripadvisor.co.uk/LocationPhotoDirectLink-g186534-d189013-i267091061-Pollok_Country_Park-Glasgow_Scotland.html

I would like to illuminate the windows which make my image mystery. The test shots will be taken during the weekend.

Equipment

- 50 mm lens

- led light and torch

- tripod

- LCD Timer Remote Shutter Release Controller

I made test shots, unfortunately, the place is open 7.30am-4.00pm so it won’t be possible to make my project there. I am so disappointed:(

We made an experiments at the studio.Using a variety of light source (large torch, phones torches, flash light)we painted with light.Our aim was to find the balance between aperture ,shutter speed and speed light power.

Our final image was layered in Photoshop.We took four separate photos of every kind of light individually.

Camera settings:f22 ISO100 13 sec

New location

My final image for Illuminate project

This image was created from the combination of 3 photographs.

EVALUATION

I always like painting with light technique especially for still life. I use this technique in my personal project because I like how many different results it can give us. Using a different source of lights we can create a wide range of images using the same objects and composition. Playing with the intensity of light, its size, power and distance from the objects we might create incredible images.

Project Illuminate was quite demanding for me because I’ve never tried to photograph such a big object with this technique. At the very beginning, I made recognition at the potential location. I’ve found perfect location but the place was closed to early to could be photographed after twilight. I was disappointed and have to find another location. I chose a place near to my home to get there easily at the proper time of the day.

I use my husband to help me because the place was dangerous and I need someone who might press the shutter button. As a source of light, I planned to use the torch but at the location, I noticed that the stream of the light was too narrow and gave to a strong, point light. My aim was to illuminate the whole object with even amount of light.

I decided to take 3 separate photographs and then combined them as one. I used 15 sec exposure time and a short distance to the object for each photograph. My aim was to avoid strong noise which is caused by long exposure time. As we know the longer exposure time the sensor made wormer what cause noise at the image. We might avoid that applying a shorter time when few people at the same time illuminate different part of the composition. I have to light the object on my own so I had to find a different solution. Even though I had to use a quite long exposure to achieve a desired amount of light. I used my phone’s torch which gives more even lighting due to the rectangular shape.

In post production with the help of my classmate, I combined the 3 photographs in one image. Using the eraser tool we uncovered the proper part of the image. At the final image, light appears on the 3 different objects.

I am not totally happy with my final image. I like the lighting and the mood but the image seems to be too dark. I chose the location with many trees which cover all the sky. The sky could create a nice contrast. The details on my image aren’t visible as I would like to.

This project was something new for me even though I’ve tried this technique before. I learned a lot about shooting on the location, about lighting and post-production. The next time I would definitely choose the better location. The sky is an important part of this kind of images and gives a totally different dimension to the photograph.

The next time I would like to try using a different type of lighting. I am going to use a speed light flash which is going to be a more powerful source of light and give me more opportunities to illuminate the objects in the desired way.

This project was an interesting experience and a great opportunity to learn something new.

#illuminate

0 notes

theheartofcoding · 7 years

Text

Hacker, Hack Thyself

We've read so many sad stories about communities that were fatally compromised or destroyed due to security exploits. We took that lesson to heart when we founded the Discourse project; we endeavor to build open source software that is secure and safe for communities by default, even if there are thousands, or millions, of them out there.

However, we also value portability, the ability to get your data into and out of Discourse at will. This is why Discourse, unlike other forum software, defaults to a Creative Commons license. As a basic user on any Discourse you can easily export and download all your posts right from your user page.

As a site owner, you can easily back up and restore your entire site database from the admin panel, right in your web browser. Automated weekly backups are set up for you out of the box, too. I'm not the world's foremost expert on backups for nothing, man!

Over the years, we've learned that balancing security and data portability can be tricky. You bet your sweet ASCII a full database download is what hackers start working toward the minute they gain any kind of foothold in your system. It's the ultimate prize.

To mitigate this threat, we've slowly tightened restrictions around Discourse backups in various ways:

Administrators have a minimum password length of 15 characters.

Both backup creation and backup download administrator actions are formally logged.

Backup download tokens are single use and emailed to the address of the administrator, to confirm that user has full control over the email address.

The name of the security game is defense in depth, so all these hardening steps help … but we still need to assume that Internet Bad Guys will somehow get a copy of your database. And then what? Well, what's in the database?

Identity cookies

Cookies are, of course, how the browser can tell who you are. Cookies are usually stored as hashes, rather than the actual cookie value, so having the hash doesn't let you impersonate the target user. Furthermore, most modern web frameworks rapidly cycle cookies, so they are only valid for a brief 10 to 15 minute window anyway.

Email addresses

Although users have reason to be concerned about their emails being exposed, very few people treat their email address as anything particularly precious these days.

All posts and topic content

Let's assume for the sake of argument that this is a fully public site and nobody was posting anything particularly sensitive there. So we're not worried, at least for now, about trade secrets or other privileged information being revealed, since they were all public posts anyway. If we were, that's a whole other blog post I can write at a later date.

Password hashes

What's left is the password hashes. And that's … a serious problem indeed.

Now that the attacker has your database, they can crack your password hashes with very sophisticated, large scale offline attacks, using the full resources of any cloud they can afford. And once they've cracked a particular password hash, they can log in as that user … forever. Or at least until that user changes their password.

⚠️ If you know your database was exposed, the very first thing you should do is reset everyone's password.

But what if you don't know? Should you preemptively reset everyone's password every 30 days, like the world's worst bigco IT departments? That's downright user hostile, and leads to serious pathologies of its own. But the reality is that you probably won't know when your database has been exposed, at least not until it's too late to do anything about it. So slowing the attackers down to give yourself time to deal with it is crucial.

Thus, the only real protection you can offer your users is just how good your stored password hashes are. There are two factors:

The hashing algorithm. As slow as possible, and ideally designed to be especially slow on GPUs for reasons that will become painfully obvious about 5 paragraphs from now.

The work factor or number of iterations. Set this as high as possible, without opening yourself up to a possible denial of service attack.

I've seen guidance that said you should set the overall work factor high enough that hashing a password takes at least 8ms on the target platform. It turns out Sam Saffron, one of my Discourse co-founders, made a good call back in 2013 when he selected the NIST recommendation of PBKDF2-HMAC-SHA256 and 64k iterations. We measured, and that indeed takes roughly 8ms using our existing Ruby login code on our current (fairly high end, Skylake 4.0 Ghz) servers.

But that was 4 years ago. Exactly how secure are our password hashes in the database today? Or 4 years from now, or 10 years from now? We're building open source software for the long haul, and we need to be sure we are making reasonable decisions that protect everyone. So in the spirit of designing for evil, it's time to put on our Darth Helmet and play the bad guy – let's crack our own hashes!

We're gonna use the biggest, baddest single GPU out there at the moment, the 1080 GTX Ti. As a point of reference, for PBKDF2-HMAC-SHA256 the 1080 achieves 1180 kH/s, whereas the 1080 Ti achieves 1640 kH/s. In a single video card generation the attack hash rate has increased nearly 40 percent. Ponder that.

First, a tiny hello world test to see if things are working. I downloaded hashcat. I logged into our demo at try.discourse.org and created a new account with the password 0234567890; I checked the database, and this generated the following values in the hash and salt database columns for that new user:

hash 93LlpbKZKficWfV9jjQNOSp39MT0pDPtYx7/gBLl5jw= salt ZWVhZWQ4YjZmODU4Mzc0M2E2ZDRlNjBkNjY3YzE2ODA=

Hashcat requires the following input file format: one line per hash, with the hash type, number of iterations, salt and hash (base64 encoded) separated by colons:

type iter salt hash sha256:64000:ZWVhZWQ4YjZmODU4Mzc0M2E2ZDRlNjBkNjY3YzE2ODA=:93LlpbKZKficWfV9jjQNOSp39MT0pDPtYx7/gBLl5jw=

Let's hashcat it up and see if it works:

./h64 -a 3 -m 10900 .\one-hash.txt 0234567?d?d?d

Note that this is an intentionally tiny amount of work, it's only guessing three digits. And sure enough, we cracked it fast! See the password there on the end? We got it.

sha256:64000:ZWVhZWQ4YjZmODU4Mzc0M2E2ZDRlNjBkNjY3YzE2ODA=:93LlpbKZKficWfV9jjQNOSp39MT0pDPtYx7/gBLl5jw=:0234567890

Now that we know it works, let's get down to business. But we'll start easy. How long does it take to brute force attack the easiest possible Discourse password, 8 numbers – that's "only" 810 combinations, a little over one billion.

Hash.Type........: PBKDF2-HMAC-SHA256 Time.Estimated...: Fri Jun 02 00:15:37 2017 (1 hour, 0 mins) Guess.Mask.......: ?d?d?d?d?d?d?d?d [8]

Even with a top of the line GPU that's … OK, I guess. Remember this is just one hash we're testing against, so you'd need one hour per row (user) in the table. And I have some more bad news for you: Discourse hasn't allowed 8 character passwords for some time now. So how long does it take if we try longer numeric passwords?

?d?d?d?d?d?d?d?d?d [9] Fri Jun 02 10:34:42 2017 (11 hours, 18 mins) ?d?d?d?d?d?d?d?d?d?d [10] Tue Jun 06 17:25:19 2017 (4 days, 18 hours) ?d?d?d?d?d?d?d?d?d?d?d [11] Mon Jul 17 23:26:06 2017 (46 days, 0 hours) ?d?d?d?d?d?d?d?d?d?d?d?d [12] Tue Jul 31 23:58:30 2018 (1 year, 60 days)

But all digit passwords are easy mode, for babies! How about some real passwords that use at least lowercase letters, or lowercase + uppercase + digits?

Guess.Mask.......: ?l?l?l?l?l?l?l?l [8] Time.Estimated...: Mon Sep 04 10:06:00 2017 (94 days, 10 hours) Guess.Mask.......: ?1?1?1?1?1?1?1?1 [8] (-1 = ?l?u?d) Time.Estimated...: Sun Aug 02 09:29:48 2020 (3 years, 61 days)

A brute force try-every-single-letter-and-number attack is not looking so hot for us at this point, even with a high end GPU. But what if we divided the number by eight … by putting eight video cards in a single machine? It's well within the reach of a small business budget or a wealthy individual. But dividing 38 months by 8 isn't changing the world. But if you want to talk about nation state attacks where they have the budget to throw thousands of these GPUs at the problem (1.1 days), maybe even tens of thousands (2.7 hours), then … yes. Even allowing for 10 character password minimums, you are in serious trouble at that point.

If we want Discourse to be nation state attack resistant, clearly we'll need to do better. Hashcat has a handy benchmark mode, and here's a sorted list of the strongest (slowest) hashes that Hashcat knows about benchmarked on a rig with eight (8) Nvidia GTX 1080 GPUs. Of the things I recognize on that list, bcrypt, scrypt and PBKDF2-HMAC-SHA512 stand out.

My quick hashcat results gave me some confidence that we weren't doing anything terribly wrong with the Discourse hashes in the database. But I wanted to be completely sure, so I hired someone with a background in security and penetration testing to, under a signed NDA, try cracking the hashes of two live and very popular Discourse sites we currently host.

I was provided two sets of password hashes from two different Discourse communities, containing 5,909 and 6,088 hashes respectively. Both used the PBKDF2-HMAC-SHA256 algorithm with a work factor of 64k. Using hashcat, my Nvidia 1080 Ti GPU generated these hashes at a rate of ~27,000/sec.

Common to all discourse communities are various password requirements:

All users must have a minimum password length of 10 characters.

All administrators must have a minimum password length of 15 characters.

Users cannot use any password matching a blacklist of the 10,000 most commonly used passwords.

Users can choose to create a username and password or use various third party authentication mechanisms (Google, Facebook, Twitter, etc). If this option is selected, a secure random 32 character password is autogenerated. It is not possible to know whether any given password is human entered, or autogenerated.

Using common password lists and masks, I cracked 39 of the 11,997 hashes in about three weeks, 25 from the ████████ community and 14 from the ████████ community.

This is a security researcher who commonly runs these kinds of audits, so all of the attacks used wordlists, along with known effective patterns and masks derived from the researcher's previous password cracking experience, instead of raw brute force. That recovered the following passwords (and one duplicate):

007007bond 123password 1qaz2wsx3e A3eilm2s2y Alexander12 alexander18 belladonna2 Charlie123 Chocolate1 christopher8 Elizabeth1 Enterprise01 Freedom123 greengrass123 hellothere01 I123456789 Iamawesome khristopher l1ghthouse l3tm3innow Neversaynever password1235 pittsburgh1 Playstation2 Playstation3 Qwerty1234 Qwertyuiop1 qwertyuiop1234567890 Spartan117 springfield0 Starcraft2 strawberry1 Summertime Testing123 testing1234 thecakeisalie02 Thirteen13 Welcome123

If we multiply this effort by 8, and double the amount of time allowed, it's conceivable that a very motivated attacker, or one with a very sophisticated set of wordlists and masks, could eventually recover 39 × 16 = 624 passwords, or about five percent of the total users. That's reasonable, but higher than I would like. We absolutely plan to add a hash type table in future versions of Discourse, so we can switch to an even more secure (read: much slower) password hashing scheme in the next year or two.

After this exercise, I now have a much deeper understanding of our worst case security scenario, a database compromise combined with a sophisticated offline password hashing attack. I can also more confidently recommend and stand behind our engineering work in making Discourse secure for everyone. So if, like me, you're not entirely sure you are doing things securely, it's time to put those assumptions to the test. Don't wait around for hackers to attack you — hacker, hack thyself!

[advertisement] At Stack Overflow, we put developers first. We already help you find answers to your tough coding questions; now let us help you find your next job.

from Coding Horror http://ift.tt/2svVFqR

#Coding Horror

0 notes